agentleFS
SauravSrivastavSauravSrivastav/claude-code-production-starter/.claude/skills/review-change/SKILL.md

review-change

Skill0 starsChanged 5 months agoMITView on GitHub

Review the current uncommitted change for defects, regressions, security issues, and missing tests.

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 25 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the complete diff and surrounding implementation.

    line 9
  2. Distinctive:

    Verify every finding against the code.

    line 11
  3. Distinctive:

    Do not edit files during this workflow.

    line 16

“Common” is measured: kept by at least 6 in 10 of the 25 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

Review the current change as a senior engineer.

  1. Read the complete diff and surrounding implementation.
  2. Prioritize behavioral defects, regressions, security risks, and missing tests.
  3. Verify every finding against the code.
  4. Lead with findings ordered by severity and include file references.
  5. State clearly when no issues are found.
  6. End with remaining test gaps or residual risk.

Do not edit files during this workflow.

Download now (ZIP)

  • Other versions28 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 28

    1. ben-manes/caffeine★ 18ksame name
    2. maypok86/otter★ 2.7ksame name
    3. aquaproj/aqua-registry★ 396same name
    4. Esri/calcite-design-system★ 376same name
    5. yiming-liao/intor★ 211same name
    6. gtrabanco/agentic-workflow★ 22same name
    7. fathomise/MailFathom★ 20same name
    8. Krzysztof318/MailFathom★ 20same name
    9. Indium-AI-Labs/indium-agentkit★ 18same name
    10. Ionate-Technologies/indium-agentkit★ 17same name

    18 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 plan-change, implement-change and 7 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.
    • BanKnightSkill

      plan-change

      将已完成 spec/design 的 change 拆成可执行 plan 与 tasks。用户要把设计落成执行计划、任务清单或实现步骤时使用。

      Also in 7 projects that use this

    • Codagent-AISkill

      implement-change

      Implements an approved change in one continuous session, with tiered test runs. Use when asked to implement a change from its approved definition, or to invoke codagent:implement-change.

      Also in 6 projects that use this

    • MaheshAwasareSkill

      write-runbook

      Generate an operational runbook for a service from its code, config, and dependencies — what to do when it breaks, where to look, how to roll back, who to escalate to. Use proactively before a service goes to production, after a major incident, or when handing off operational ownership.

      Also in 3 projects that use this

    • testified-ossSkill

      incident-triage

      Triage production incidents with severity assessment, root cause hypothesis, impact analysis, and escalation recommendations. Use when analyzing outages, errors, or production issues.

      Also in 4 projects that use this

    • srclightSkill

      refactor-safely

      This skill should be used when the user asks to "refactor", "rename", "move", "change a function signature", "extract a method", "delete unused code", "clean up", or any modification that could break callers or dependents. Provides a pre-change safety checklist using srclight's graph tools to assess blast radius before touching code.

      Also in 3 projects that use this

    • Google CloudSkill

      open-pr

      Commits local changes to a new Git branch and opens a GitHub pull request through the configured GitHub MCP server. Use when proposing code changes in a new pull request. Don't use for local-only commits without a remote GitHub repository.

      Also in 4 projects that use this

  • In this repository3 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.

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.