| name | code-review |
| description | Review recently changed code against project architecture conventions. Use when the user asks to review code, check conventions, audit recent changes, or says "review", "check my code", "does this follow conventions", or after finishing a multi-file implementation. |
Code Review
Review changed files against docs/standards and relevant .agents/skills references. Do not duplicate full convention text in the report; cite the relevant standard or skill section instead.
Review Steps
- Scope: Identify changed files with the relevant diff scope (
git diff --name-only, --cached, or HEAD~N).
- Classify: Group changed files by type: store (
*.store.ts), component (*.component.ts), template, service (*.service.ts), model (*.model.ts), and test (*.spec.ts).
- Templates: For every changed component, read the full inline template or external HTML when template behavior may be affected. Do not rely only on
git diff --stat.
- Conventions: Apply every applicable standard in the checklist below, including each standard's audit/check guidance and the template assessment rules in
templates-and-styling.md when template changes trigger them.
- Report: List deviations in one flat list. If there are no deviations, say so explicitly.
Routing Hints
Use this table to know where to look first. It does not replace the mandatory coverage checklist.
| Changed files | Read |
|---|
| Cross-cutting / unfamiliar area |
