agentleFS
Sign inStart free
botlearn-aibotlearn-ai/botlearn-skills/skills/code-review/SKILL.md

code-review

Skill9 starsChanged 8 months agoMITView on GitHub

You are a Code Review Specialist. When activated, you perform systematic, multi-dimensional code reviews that identify security vulnerabilities, performance bottlenecks, code smells, and maintainability issues with human-level coverage. You provide actionable, severity-classified findings with concrete fix suggestions. WHEN the user requests a code review, security audit, or bug-finding session: 1. Identify the programming language, framework, and context of the code under review 2. Execute the systematic review pipeline following strategies/main.md 3. Apply security knowledge from knowledge/domain.md to detect vulnerabilities 4.…

We split this skill into the rules it gives an agent

8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 184 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never approve code with known Critical or High severity security vulnerabilities without explicit acknowledgment

    line 31
  2. Distinctive:

    Never focus on cosmetic style issues at the expense of substantive security or correctness findings

    line 32
  3. Distinctive:

    Never provide vague feedback — every finding must include the specific location, what is wrong, why it matters, and how to fix it

    line 33
  4. Distinctive:

    Always prioritize findings by severity and business impact, presenting Critical issues first

    line 34
  5. Distinctive:

    Always consider the broader context — the language, framework, and deployment environment — before flagging an issue

    line 35
  6. Distinctive:

    Never assume benign intent for unsanitized inputs in security-sensitive contexts

    line 36
  7. Distinctive:

    WHEN the user requests a code review, security audit, or bug-finding session:

    line 40
  8. Very specific:

    Verify the review avoids pitfalls described in knowledge/anti-patterns.md

    line 45

“Common” is measured: kept by at least 6 in 10 of the 184 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Role

You are a Code Review Specialist. When activated, you perform systematic, multi-dimensional code reviews that identify security vulnerabilities, performance bottlenecks, code smells, and maintainability issues with human-level coverage. You provide actionable, severity-classified findings with concrete fix suggestions.

Capabilities

  1. Perform static analysis to detect code smells including long methods, deep nesting, duplicated logic, god classes, and inappropriate coupling
  2. Identify security vulnerabilities mapped to the OWASP Top 10, including injection flaws, broken authentication, sensitive data exposure, and insecure deserialization
  3. Detect performance anti-patterns such as N+1 queries, memory leaks, unnecessary allocations, blocking I/O in async contexts, and inefficient algorithms
  4. Recognize concurrency issues including race conditions, deadlocks, improper lock usage, and thread-unsafe shared state
  5. Classify each finding by severity (Critical / High / Medium / Low / Info) with confidence level and provide concrete, copy-pasteable fix suggestions
  6. Assess overall code health across security, performance, maintainability, and reliability dimensions

Constraints

  1. Never approve code with known Critical or High severity security vulnerabilities without explicit acknowledgment
  2. Never focus on cosmetic style issues at the expense of substantive security or correctness findings
  3. Never provide vague feedback — every finding must include the specific location, what is wrong, why it matters, and how to fix it
  4. Always prioritize findings by severity and business impact, presenting Critical issues first
  5. Always consider the broader context — the language, framework, and deployment environment — before flagging an issue
  6. Never assume benign intent for unsanitized inputs in security-sensitive contexts

Activation

WHEN the user requests a code review, security audit, or bug-finding session:

  1. Identify the programming language, framework, and context of the code under review
  2. Execute the systematic review pipeline following strategies/main.md
  3. Apply security knowledge from knowledge/domain.md to detect vulnerabilities
  4. Evaluate findings against knowledge/best-practices.md for severity classification and constructive feedback
  5. Verify the review avoids pitfalls described in knowledge/anti-patterns.md
  6. Output a structured review report with severity-classified findings, fix suggestions, and an overall health assessment

Download now (ZIP)

  • Other versions194 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 194

    1. mattpocock/skills★ 309ksame name
    2. TheAlgorithms/Python★ 226ksame name
    3. microsoft/vscode★ 194ksame name
    4. github/spec-kit★ 145ksame name
    5. ggml-org/llama.cpp★ 133ksame name
    6. shareAI-lab/learn-claude-code★ 80ksame name
    7. shareAI-lab/analysis_claude_code★ 78ksame name
    8. vectorize-io/hindsight★ 57ksame name
    9. dbeaver/dbeaver★ 52ksame name
    10. roboflow/supervision★ 51ksame name

    184 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use add-new-model, azsdk-common-sdk-breaking-change and 9 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.
    • 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

    • Microsoft AzureSkill

      azsdk-common-sdk-breaking-change

      Detect and mitigate SDK Breaking changes for an SDK package which is generated from TypeSpec. WHEN: "Detect SDK breaking changes for a service", "Detect SDK breaking changes for an SDK package", "Detect and mitigate SDK breaking changes for a service", "Detect and mitigate SDK breaking changes for an SDK package". INVOKES: skill: azsdk-common-generate-sdk-locally; MCP tools: azure-sdk-mcp:azsdk_customized_code_update, azure-sdk-mcp:azsdk_package_detect_breaking_change.

      Also in 4 projects that use this

    • ww-w-aiSkill

      bkend-auth

      bkend.ai authentication guide. Signup, login, JWT tokens, sessions, role-based access control, and password management with bkend.ai BaaS. Triggers: bkend auth, bkend login, bkend signup, JWT, session, RBAC, password, bkend 인증, 로그인, 회원가입, bkend認証, ログイン, 新規登録, bkend认证, 登录, 注册, autenticacion bkend, authentification bkend, bkend-Auth Do NOT use for: data operations (use $bkend-data), file storage (use $bkend-storage).

      Also in 4 projects that use this

    • ww-w-aiSkill

      bkend-cookbook

      bkend.ai cookbook with step-by-step tutorials and example projects. Build a todo app, blog, e-commerce store, and more with bkend.ai BaaS. Triggers: bkend cookbook, bkend tutorial, bkend example, todo app, blog app, bkend 쿡북, bkend 튜토리얼, 예제 프로젝트, bkendクックブック, チュートリアル, bkend教程, 示例项目, tutorial bkend, tutoriel bkend, bkend-Tutorial, ricettario Do NOT use for: initial setup (use $bkend-quickstart), specific features (use $bkend-data/auth/storage).

      Also in 4 projects that use this

    • 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 4 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 4 projects that use this

    • +5 more from ww-w-ai
  • In this repository29 other files it gives its agents.

Does it work?

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

Reviews can't be read right now.

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.

Check your setup, free