A workflow decides which specialists touch the work and in what order. Small changes should not pay for a full review cohort, and a risky migration should not skip one.
Narrow roles beat one generalist told to do everything. Each specialist gets the context it needs and none of the context it does not, which is most of what keeps quality and cost in line.
Turns the brief into a change plan with acceptance criteria and a test approach, using repo profiles and the wiki.
Challenges the spec and the diff: missed cases, contract changes, anything that drifts from house style.
Implements the approved plan in the sandbox, on a branch, keeping to the conventions in the repo profile.
Writes and runs tests against the repo's own commands, and reports honestly when something does not pass.
Turn it on for auth, payments, data handling, or any path you mark as sensitive.
Looks at the change in the context of the whole system rather than the diff in isolation.
Agents, workflows, skills and MCP servers, in verified and community tiers. Install one, fork it, and change it to match how your organisation works.
Browse it after signup →A gate pauses a run and asks a specific question. You get notified, you answer, the run carries on. Place them where your risk actually is, and leave them off everywhere else.