agentleFS
brianbolzebrianbolze/truffle/.claude/skills/agent-build-review/SKILL.md

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).

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
  1. Distinctive:

    Read before reviewing — these carry the rules.

    line 36
  2. Distinctive:

    Read the context above, then read the artifact itself — actually read it.

    line 46
  3. Distinctive:

    Write findings first, then a recommended lean (in the lead's decision vocabulary — see reviewer-context — or plain words if none fits), …

    line 49
  4. Distinctive:

    Stop. Don't decide; don't edit the artifact.

    line 54

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

$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

  1. Resolve the mode — first argument (frame | proposal | change), inferred from the target if omitted. One artifact per run.
  2. Read the context above, then read the artifact itself — actually read it; don't critique from memory.
  3. Critique against the mode's rubric and the reviewer disciplines.
  4. 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.
  5. Out-of-scope thing worth remembering? Log an observation per learning/AGENTS.md — capture only, never a fix.
  6. 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.

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.