Receiving Code Review

Use when retiring old logic, collapsing duplicate owners, removing fallbacks, or touching schema, persistence, or source-of-truth boundaries...

Use when defining new features, product behavior, UI/component design, architecture choices, contract changes, or ambiguous medium/high-comp...

Use when the user asks for caveman mode, fewer tokens, brief responses, compressed communication, or otherwise explicitly requests a much sh...

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

Use when the user asks to establish shared project language or project work exposes a resolved, vague, conflicting, renamed, or deprecated d...

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Use when verified work has an Aegis-created branch/worktree to integrate or clean up, or the user explicitly requests merge, PR, or branch l...

Use when explicitly asked for first-principles or Occam's-razor review, or when complex decisions involve competing constraints, repeated fi...

Use when the user explicitly sets an Aegis goal with /aegis-goal, Aegis goal:, or asks to define goal, success evidence, stop condition, or...

Use when a task is multi-step, may span context resets or sessions, uses subagents, or risks losing state before completion.

Use when the user asks to create, write, update, amend, supersede, or evaluate an ADR, architecture decision record, durable architecture de...

Use when requesting independent code review, after implementation slices, before merging high-risk work, or when verification exposes eviden...

Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests,...

A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.

Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold e...

Use when you need to resolve an in-progress git merge/rebase conflict.

A relentless interview that asks every frontier question at once, round by round.