agent-build-review
Skill1 starsChanged 5 months agoApache-2.0View on GitHub
Independently critique one Agentic Build artifact — a frame, a proposal, or an implemented change — surfacing findings plus a recommended lean, never a decision. Use when explicitly asked to run agent-build-review, or to get an independent review of a frame/proposal/change before the lead decides. NOT the learning-consolidation pass (that's learning-review).
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-build-decideSkill
- agent-build-proposeSkill
- agent-learning-mineSkill
- commit-allSkill
- learning-reviewSkill
- market-read-labSkill
- review-changeSkill
- work-menuSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
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
- Distinctive: line 36
Read before reviewing — these carry the rules.
- Distinctive: line 46
Read the context above, then read the artifact itself — actually read it.
- Distinctive: line 49
Write findings first, then a recommended lean (in the lead's decision vocabulary — see reviewer-context — or plain words if none fits), …
- Distinctive: line 54
Stop. Don't decide; don't edit the artifact.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
$ARGUMENTS
Purpose
Give one independent critique of a single Agentic Build artifact — a frame, a
proposal, or an implemented change. Surface findings and a recommended lean so the
lead can decide. You do not decide (accept / revise / park / cut / merge is the
lead's call, or Brian's), and you do not edit what you review.
Independence — spawn if you authored it
Independent review is required; self-review is not enough.
- You authored the artifact this session (wrote the frame/proposal, or made the
change) → spawn a fresh sub-agent to review it. Give it a short kickoff brief — why
it's reviewing, the goal, the mode, and what to read — per
effective-prompts.md(#8: the why + goal + pointers, not the how). Reviewing is judgment — let the reviewer inherit the main model. - You didn't author it → you're already independent; review directly.
The boundary — when each mode runs
proposal mode gates the plan, before any code; change mode audits the patch, after, against the accepted proposal. That ordering is the point — it's what lets review gate instead of narrate retrospectively.
So if you're asked for a proposal review but the packet has already shipped (proposal.md says Status: implemented, carries a receipt, or the change is already in the tree), the plan/patch boundary collapsed. Don't fake a retrospective plan review and don't invent a post-hoc mode — flag the collapse as your top finding, then audit the patch in change mode against the proposal as written.
Required context
Read before reviewing — these carry the rules; don't restate them:
2026-06-24-reviewer-context.md— reviewer disciplines, what to stress per mode, the lean to recommend, current posture.- The rubric reviewer-context names for your mode, plus the packet's own docs (frame.md / proposal.md / the diff + the accepted proposal).
Task
- Resolve the mode — first argument (
frame|proposal|change), inferred from the target if omitted. One artifact per run. - Read the context above, then read the artifact itself — actually read it; don't critique from memory.
- Critique against the mode's rubric and the reviewer disciplines.
- Write findings first, then a recommended lean (in the lead's decision vocabulary — see reviewer-context — or plain words if none fits), clearly marked as a recommendation.
- Out-of-scope thing worth remembering? Log an observation per
learning/AGENTS.md— capture only, never a fix. - Stop. Don't decide; don't edit the artifact.
Output
- With a packet → write findings to it:
frame→frame-review.md,proposal→proposal-review.md,change→packet-review.md. - Standalone (no packet) → return the findings inline.
Final response
End with:
- review path (or
inline) - mode + what was reviewed
- findings, most important first
- recommended lean — marked as a recommendation; the lead decides
No decision was made; the reviewed artifact was not edited.
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
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.

