julian
17c08e6392
- Nx 22.7 monorepo (pnpm 11.1, TypeScript 5.9, Node 24) - apps/api: NestJS 11 (CJS conforme CODING-RULES.md PGD-DB-004) - apps/web: React 19 + Vite 8 (ESM) - libs/shared/api-interface: Zod contract base - Docker Compose dev: Postgres 18, Valkey 8, MinIO, Mailpit - WDS artifacts: - design-artifacts/A-Product-Brief/ (5 docs canônicos + 16 dialogs) - design-artifacts/B-Trigger-Map/ (hub + 4 personas + feature impact) - Stack canon: STACK.md v2.2 + CODING-RULES.md v2.0 + brand.md - AGENTS.md + README.md como entrada para devs/agentes Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1.9 KiB
1.9 KiB
Generate Review Trail
Generate a review trail from the diff and codebase context. A generated trail is lower quality than an author-produced one, but far better than none.
Follow Global Step Rules in SKILL.md
INSTRUCTIONS
- Get the full diff against the appropriate baseline (same rules as Surface Area Stats in step-01).
- Read changed files in full — not just diff hunks. Surrounding code reveals intent that hunks alone miss. If total file content exceeds ~50k tokens, read only the files with the largest diff hunks in full and use hunks for the rest.
- If a spec exists, use its Intent section to anchor concern identification.
- Identify 2–5 concerns: cohesive design intents that each explain why behind a cluster of changes. Prefer functional groupings and architectural boundaries over file-level splits. A single-concern change is fine — don't invent groupings.
- For each concern, select 1–4
path:linestops — locations where the concern is most visible. Prefer entry points, decision points, and boundary crossings over mechanical changes. - Lead with the entry point — the highest-leverage stop a reviewer should see first. Inside each concern, order stops so each builds on the previous. End with peripherals (tests, config, types).
- Format each stop using
path:lineper the global step rules:
**{Concern name}**
- {one-line framing, ≤15 words}
`src/path/to/file.ts:42`
When there is only one concern, omit the bold label — just list the stops directly.
PRESENT
Output after the orientation:
I built a review trail for this {change_type} (no author-produced trail was found):
{generated trail}
The generated trail serves as the Suggested Review Order for subsequent steps. Set review_mode to full-trail — a trail now exists, so all downstream steps should treat it as one.
If git is unavailable or the diff cannot be retrieved, return to step-01 with: "Could not generate trail — git unavailable."