agentleFS
kunalsurikunalsuri/ai-fication-kit/.agents/skills/review-change/SKILL.md

review-change

Skill3 starsChanged 4 months agoApache-2.0View on GitHub

Review a completed change against its authorizing spec in fresh context — evidence-based checks, severity-ranked findings, and a written verdict for the human's merge decision. Use when a diff needs reviewing before merge, or when add-feature / fix-bug / implement-spec reaches its review gate.

32 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use plan-change, implement-change and 8 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 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

  • Sagargupta16Skill

    upgrade-dependencies

    Upgrade a project's dependencies one at a time, running the test suite after each bump and reverting the ones that break it. Use it during routine dependency maintenance, when a batch of updates has accumulated; before a major release, to go into it on current and patched dependencies; when Renovate or Dependabot PRs have piled up and you want them resolved locally in one sitting; when a security advisory means you need the patched version in, and you need to know what it breaks.

    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

The file

Files
SKILL.md
<!-- Copyright (c) 2026 Kunal Suri (CEA LIST). All rights reserved. -->

Review a change

The contract: review in a session that did NOT write the change; check with evidence, not assertions; re-run the suites yourself; the written verdict is the deliverable — the human merges, not you.

1. Fresh-context gate

A reviewer sharing the implementer's context inherits the implementer's blind spots. If this session wrote the change, stop and hand the review to a fresh session that did not implement it.

2. Pin the scope

Identify the exact diff (commits / branch / files) and the spec or bugfix doc in ai/lab/specs/ that authorized it. No spec ⇒ that is finding #1, severity blocker: unspecced work.

3. Open the review

Copy ai/lab/reviews/REVIEW_TEMPLATE.md → ai/lab/reviews/REVIEW_<work-id>.md.

4. Check with evidence

For each check in the template — spec conformance, surgical diff, Stability respected, tests, conventions, knowledge updated, provenance clean — record where you looked and what you saw. Re-run the suites the spec names yourself; do not trust the implementer's report.

5. File findings by severity

Any blocker or major ⇒ verdict request-changes; hand the list back to the implementer. Minor / nit findings can ship with notes.

6. Verdict and hand-off

Fill "what the human should double-check" — the judgement calls a mechanical check cannot make. The review itself is [inferred]; the human's merge decision is the real approval, and this document is its evidence.

7. Record

Link the review from the work's row in ai/lab/WORKLOG.md (Review column) and set that row's Status to in-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.