execute-review

name	execute-review
description	Execute a code review for implemented work by analyzing git diff, reading modified files, checking project rules and skills, verifying Tech Spec and task adherence, running tests, identifying code quality issues, and saving a code review report. Use when Codex is asked to review code, validate implementation quality, approve changes, or produce codereview.md for a feature or project change.

Execute Review

Use this skill to review implemented code against the Tech Spec, tasks, and project standards.

Required Workflow

1. Analyze documentation.

   • If the review is feature-specific, identify the feature folder under tasks/prd-[feature-name]/.
   • Read techspec.md to understand expected architectural decisions.
   • Read tasks.md and relevant individual task files to verify implemented scope.
   • Read applicable project rules under .codex/rules/.
   • Read applicable project skills under .codex/skills/.

2. Analyze code changes.

   • Use git diff to inspect produced code changes.
   • Use git status to identify modified, added, deleted, and untracked files.
   • Read the full code of modified files, not just the diff.
   • Check whether any expected files or tests should have been changed but were not.

3. Check rules compliance.

   • Verify naming standards, folder structure, formatting, linting, dependencies, error handling, logging, language conventions, and other applicable project rules.
   • Do not flag a rule violation without first checking the relevant rule file.

4. Check Tech Spec adherence.

   • Compare implementation against documented architecture, components, interfaces, contracts, data models, endpoints, and integrations.
   • Flag missing or divergent implementation with file and line references where possible.

5. Check task completeness.

   • For each completed task, verify corresponding code was implemented.
   • Confirm acceptance criteria, subtasks, and task tests were completed.

6. Run verification.

   • Run the project’s relevant test suite, type checks, lint checks, and builds.
   • Check that new tests exist for new behavior and are meaningful.
   • The review cannot be approved while required tests fail.

7. Analyze code quality.

   • Check complexity, duplication, naming, comments, error handling, security, performance, maintainability, and impact on other parts of the system.
   • Prioritize bugs, regressions, rule violations, security risks, and missing tests over style preferences.

8. Save the review report.

   • Use references/code-review-report-template.md.
   • Save to tasks/prd-[feature-name]/codereview.md when the review is feature-specific.
   • Otherwise save to codereview.md at the project root.
   • Set status to APPROVED, APPROVED WITH RESERVATIONS, or REJECTED based on the approval criteria.

Approval Criteria

• APPROVED: All criteria are met, tests pass, and code complies with rules and Tech Spec.
• APPROVED WITH RESERVATIONS: Main criteria are met, but non-blocking improvements remain.
• REJECTED: Tests fail, serious rule violations exist, implementation diverges from the Tech Spec, required task work is missing, or security issues exist.

Hard Rules

• Use git diff to analyze code changes.
• Read the full code of modified files, not only the diff.
• Check project rules before flagging issues.
• Check project skills when relevant to the implementation.
• Verify the implementation follows the Tech Spec and tasks exactly.
• Do not approve the review while required tests fail.
• Always save the final report as codereview.md in the correct location.

Quality Checklist

• Tech Spec was read and understood.
• Tasks were verified.
• Project rules were reviewed.
• Project skills were reviewed when applicable.
• Git diff and status were analyzed.
• Full modified files were read.
• Rules compliance was verified.
• Tech Spec adherence was checked.
• Completed tasks were validated.
• Tests were run and passing, or failures were documented with REJECTED status.
• Code quality and code smells were checked.
• Final report was saved.