agentleFS
ZhouYinLong-labZhouYinLong-lab/Dog-Skills/code-review/SKILL.md

code-review

Skill7 starsChanged 5 months agoMITView on GitHub

代码审查元技能——整合两种互补的审查模式:(1) standard 五维审查(安全性·性能· 可维护性·规范·边界情况),5 个 Agent 并行+置信度过滤;(2) adversarial 对抗式审查 (恶意用户视角,"我要搞崩你的系统"),逻辑漏洞·隐藏 Bug·思维盲点。 两种模式覆盖从工程质量把关到破坏性测试的完整审查链路。 Trigger keywords: code review, 代码审查, 多Agent审查, 并行审查, 代码质量检查, PR review, 安全审查, 性能审查, 边界检查, review my code, 帮我审查代码, adversarial review, 对抗式审查, 对抗性审查, red team, 找BUG, 挑毛病, 攻击测试, 渗透测试思维, 恶意用户视角, 代码审计, 提交前检查, pre-commit review.

194 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use close-spec, design-with-images and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • dzhngSkill

    close-spec

    When a spec under specs/<feature>/ is done shipping (a write-spec build, or any planned task that produced a spec), archive it to specs/done/ and rewrite it from a build-plan into a durable rationale — the why, the principles, the invariants — pointing back to the real code for the how. Use when implementation has landed and the plan no longer matches what shipped, or the user says a feature/spec is finished. Pairs with [write-spec](../write-spec/SKILL.md) (the plan this closes) and [review](../review/SKILL.md) (run before closing).

    Also in 5 projects that use this

  • dzhngSkill

    design-with-images

    Explore UI and visual design with image generation, then iterate the real implementation against the user-selected concept. Use when brainstorming visual directions, offering mockup variants, or implementing an approved generated design; do not stop at the mockups or the first code approximation.

    Also in 5 projects that use this

  • PydanticSkill

    add-new-model

    Add support for a newly-released language or image generation model in pydantic-ai (e.g. openai:gpt-5.6, anthropic:claude-sonnet-5, openai:gpt-image-2). Use when a provider ships a new model id and you need to wire literals, profile flags, adapters, and tests to recognize it. Handles SDK-lag, gateway list conventions, capability probing, and direct image-model geometry.

    Also in 9 projects that use this

  • transitive-bullshitSkill

    compare-screenshots

    Compare screenshots against the intended design, distinguishing approved references from historical baselines. Use for iterative implementation matching, before/after visual review, objective image telemetry, or checking a lone capture for flat, empty, or badly framed content.

    Also in 5 projects that use this

  • Microsoft AzureSkill

    azsdk-common-apiview-feedback-resolution

    Analyze and resolve APIView review feedback on Azure SDK PRs. **UTILITY SKILL**. USE FOR: APIView comments, API review feedback, SDK API surface changes. DO NOT USE FOR: general code review, non-APIView feedback. INVOKES: azure-sdk-mcp:azsdk_apiview_get_comments, azure-sdk-mcp:azsdk_customized_code_update, azure-sdk-mcp:azsdk_typespec_delegate_apiview_feedback, azure-sdk-mcp:azsdk_run_typespec_validation, azure-sdk-mcp:azsdk_package_generate_code.

    Also in 6 projects that use this

  • Microsoft AzureSkill

    azsdk-common-generate-sdk-locally

    Generate and finalize Azure SDKs locally from TypeSpec, including build, checks, tests, changelog, metadata, and version updates by default. WHEN: "generate SDK locally", "build SDK", "run SDK tests", "run CI checks", "validate package", "run checks", "update changelog", "fix SDK build errors", "resolve SDK generation errors", "customize TypeSpec", "rename SDK client", "rename SDK model", "hide operation from SDK", "fix analyzer errors", "resolve customization drift", "create subclient", "update metadata", "update version". INVOKES: azsdk_verify_setup, azsdk_package_generate_code, azsdk_package_build_code, azsdk_package_run_check, azsdk_package_run_tests, azsdk_customized_code_update, azsdk_package_update_changelog_content, azsdk_package_update_metadata, azsdk_package_update_version.

    Also in 6 projects that use this

  • +4 more from dzhng
  • +2 more from Azure

The file

Files
SKILL.md

Code Review — 双模式代码审查元技能

两种互补的审查模式:standard 把关工程质量,adversarial 模拟攻击者视角。覆盖从常规 PR 到安全审计的完整审查链路。

两种模式

┌──────────────────────────────────────────────────────────────┐
│                    Code Review                                 │
│                                                               │
│  /review standard     ── 五维工程质量审查                      │
│  /review adversarial  ── 恶意用户视角破坏性测试                │
└──────────────────────────────────────────────────────────────┘

Standard 模式 — 五维工程质量审查

5 个 Agent 并行审查 + 置信度过滤:

代码 → 安全Agent · 性能Agent · 可维护Agent · 规范Agent · 边界Agent
         │
         ▼
    置信度过滤(自动剔除假阳性)
         │
         ▼
    Critical → High → Medium → Low 分级报告

何时用:日常 PR、提交前检查、重构后验证。


Adversarial 模式 — 对抗式审查

AI 换一个身份,从"我要用各种奇怪的数据搞崩你的系统"出发:

恶意用户视角 → 多Agent并发扫描
    │
    ├── 逻辑漏洞:"这个判断条件有没有反例?"
    ├── 安全风险:"注入/XSS/权限绕过?"
    ├── 边界条件:"传null/负数/超大值会怎样?"
    ├── 隐藏Bug:"并发/竞态/死锁?"
    └── 思维盲点:"你没想到什么?"

何时用:安全审计、核心模块上线前、被攻击后的排查。


使用方式

你说模式
"帮我审查代码" / /code-reviewStandard(默认)
"审查 PR 的代码质量"Standard
"帮我做对抗式审查" / "以攻击者视角审查"Adversarial
"全面审计——先 standard 再 adversarial"双模式串联

推荐流水线

Code Simplifier(先优化结构)
       │
       ▼
Code Review standard(工程质量把关)
       │
       ▼
Code Review adversarial(安全+边界兜底)
       │
       ▼
人工 Review

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.