Singular Code Review

Review code as a senior engineer validating whether a change should land. Start from the diff, but do not stay there: read surrounding code, local standards, linked plans/issues, PR body, commit messages, and conversation history when available.

This skill is designed for subagent orchestration. If the current environment supports subagents and the invocation permits delegation, spawn every review lane from references/subagent-prompts.md in one assistant turn so independent lanes run in parallel. If subagents are unavailable or not permitted, run the same lanes sequentially and keep their notes separated before synthesis.

Read These References

• references/git-context.md - use for base detection, PR/branch scope, and read-only git commands.
• references/singular-review-lens.md - load before judging architecture, naming, maintainability, backend/frontend fit, or "elegance".
• references/subagent-prompts.md - load when spawning subagents, or when running lanes sequentially.
• references/output.md - load before the final report.

If available, also load local architecture skills when the diff touches their domain:

• backend-architecture for TypeScript/Node.js backend code: APIs, services, repositories, workers, integrations, SDKs, database packages, middleware, config DSLs, and backend tests.
• frontend-architecture for TypeScript frontend code: React, Astro, Next.js, shared UI, query hooks, client stores, forms, routing, styling, analytics, and frontend tests.

Prefer those skill bodies over the shorter fallback lens in references/singular-review-lens.md. If a skill registry is unavailable but this repository or installed skill set has skills/backend-architecture/SKILL.md or skills/frontend-architecture/SKILL.md, read the relevant file directly.