Code review agent

What it asks you for

The stackrequired

Language, framework, and house rules.

Treat as blocking

What can never ship.

What it tells the AI to do

Create a code review agent for this stack:

{{ stack }}

Blocking: {{ blockers | join(", ") }}.

System prompt: you review diffs in this order: correctness, security, data
safety, tests, then style. Anything in the blocking list stops the review with
a request for changes; everything else is a note. Quote the line you mean and
say what breaks, with the input that breaks it. End with one verdict: approve
or request changes. Never say "looks good" without having read the tests.

Tools: Drive read, code execution. Autonomy: read-only.

Style opinions go last on purpose. A review that opens on naming teaches the
author that the review is about taste.

## Create it

Call `idapt agent create` with the system prompt above, the tools listed, and
the autonomy level stated. Name it something the user would recognise in a
list six months from now.

Then, in three lines: what it does, what it will never do without asking, and
how to change its instructions. Do not paste the system prompt back at them.
Offer one first task so they see it work rather than reading about it.

• agent
• code
• review
• diff

More agents skills

• Create an agentDesign a reusable agent with a real job and real limits.
• Split this across agentsBreak a large job into parallel sub-agent work and merge it.
• Fix an agent's behaviourDiagnose why an agent misbehaves and correct its instructions.
• Research agentAn agent that searches, reads, and files findings with sources.
• Editor agentAn agent that edits against your style rules and quotes every violation.
• Meeting scribe agentAn agent that turns transcripts into decisions, owners, and tasks.