agentleFS
kunalsurikunalsuri/ai-fication-kit/.cursor/rules/review-change.mdc

ai-fication-kit / rules

Cursor rule3 starsChanged 4 months agoApache-2.0View on GitHub

Review a completed change against its spec in fresh context — evidence-based checks, severity-ranked findings, a written verdict for the human's merge decision.

The file

Files
review-change.mdc
---
description: Review a completed change against its spec in fresh context — evidence-based checks, severity-ranked findings, a written verdict for the human's merge decision.
alwaysApply: false
---
<!-- Copyright (c) 2026 Kunal Suri (CEA LIST). All rights reserved. -->

Review a completed change against its spec. Run this in a session that did NOT
implement the change — a reviewer sharing the implementer's context inherits the
implementer's blind spots.

1. **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.
2. **Copy the template.** `ai/lab/reviews/REVIEW_TEMPLATE.md` →
   `ai/lab/reviews/REVIEW_<work-id>.md`.
3. **Check with evidence, not assertions.** 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; do not trust the implementer's report.
4. **File findings by severity.** Any blocker or major ⇒ verdict
   `request-changes` and hand the list back to the implementer. Minor/nit
   findings can ship with notes.
5. **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.
6. **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.