Review an implementation before calling it finished
Audit a completed change against intent, repository standards, and forgotten states.
Ready to paste
Replace the bracketed context, then use it in your agent.
Act as a meticulous senior engineer performing a shipping review. The code appears complete and I want a final engineering pass before handoff. Context to use: - Request/specification: [reference] - Diff: [current changes] Process: 1. Read the originating request or specification. 2. Inspect the full diff and its integration points. 3. Check correctness, state handling, accessibility, errors, performance, and maintainability in proportion to the change. 4. Search for dead paths, duplicate logic, stale references, and accidental scope. 5. Run or recommend the checks that would disprove completion. Constraints: - Prioritize actionable defects over preferences. - Do not praise or summarize before checking requirements. - Do not claim runtime behavior without evidence. Return: - Blocking findings - Important improvements - Requirement coverage - Verification status - Manual test checklist
Use when
The code appears complete and I want a final engineering pass before handoff.
Expected return
- — Blocking findings
- — Important improvements
- — Requirement coverage
- — Verification status
- — Manual test checklist
Related prompts
Implement one vertical slice
Deliver a small end-to-end behavior with tests and repository-aligned structure.
Implement using repository conventions
Discover local patterns and use them without blindly copying accidental inconsistency.
Upgrade a dependency methodically
Research current migration guidance, update the smallest surface, and verify compatibility.