agentleFS
Sign inStart free
taljeontaljeon/plzdo/skills/review-change/SKILL.md

review-change

Skill9 starsChanged 18 days agoMITView on GitHub

Code review by independent Claude subagents (reviewer + code-reviewer). Use whenever the user asks for a code review, asks to review or check code, and for routine review of any meaningful code change before saying done, committing, or opening a PR. Korean cues: 리뷰해줘, 검수해줘, 코드 봐줘, 커밋 전에 확인, PR 전에 봐줘. Skip docs-only, config-only, or trivial one-line changes.

29 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use plan-change, write-runbook and 5 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

  • 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

  • ShopifySkill

    prepare-release

    Prepare the changeset-release/main branch for release by syncing version.ts files and running pnpm install

    Also in 3 projects that use this

The file

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:

    Start both agents in one message so they run in parallel:

    line 12
  2. Distinctive:

    Not a git repo: list the changed files.

    line 22
  3. Distinctive:

    Treat each finding as a claim to check against the code, not as a fact.

    line 34

“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 a change

Claude-only version of the owner's codex-review flow: the second model is replaced by two Claude subagents that did not write the code. Same-model review is less independent, so keep the handoff rule strictly: give them the code and the spec, never your conclusion.

Run

Start both agents in one message so they run in parallel:

  • reviewer: spec conformance. Missing, unrequested or wrong behavior, and loosened tests.
  • code-reviewer: security, performance and bugs, with file and line evidence.

Name the target in each prompt:

  • Uncommitted work: "Review the uncommitted changes (git status, git diff HEAD, and untracked files)."
  • Branch vs base: "Review the changes on this branch against main (git diff main...HEAD)."
  • One commit: "Review the changes in commit <sha> (git show <sha>)."
  • Not a git repo: list the changed files.

Include the spec or the user's request, and the implementer's report when there is one. Leave out your own verdict.

Instructions unless the user gave others:

List only problems you would block the merge for. Check the change against the spec: anything missing, anything not asked for, anything implemented but wrong. A removed, skipped or loosened test is a finding unless the spec, request, report or diff gives the reason and names the check that now covers it, or the requirement itself was removed. For each: file and line, why it is wrong, and how to show it fails. If there are none, say so.

The reviewer agent cannot run commands. If it names a command that would settle a claim, run it yourself.

Use the result

  • Treat each finding as a claim to check against the code, not as a fact. Fix the confirmed ones and say which you rejected and why.
  • A finding caused by an unclear spec fixes the spec first, then the code.
  • Report both reviews: confirmed findings, rejected findings, and what neither covered.

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.

Check your setup, free