| name | execute-review |
| description | Execute code review for implementation changes against TechSpecs, task files, project rules, and project skills. Use when Codex is asked to review code, analyze git diff, verify tests, check rules compliance, validate TechSpec or task adherence, identify code smells, or create codereview.md at the project root or under tasks/prd-[feature-name]/. |
Execute Review
Core Workflow
Use this skill to review implementation changes against the expected technical specification, task scope, project standards, and tests.
Read resources/execute-review.md before starting. Treat that file as the canonical workflow for this skill.
Load resources/code-review-report-template.md only when generating the final codereview.md report. Treat that file as the required review report template standard.
Execution Rules
- Read the TechSpec and Tasks for the target feature when available.
- Read relevant project rules and project skills before judging compliance.
- Use
git diff to analyze changed code.
- Read the full modified files, not only the diff.
- Verify implementation adherence to the TechSpec and completed Tasks.
- Run the relevant project tests and reject the review if required tests fail.
- Check for rule violations, missing tests, code smells, security risks, and performance issues.
- Save the final report in
codereview.md at the project root, or tasks/prd-[feature-name]/codereview.md when the review is feature-specific.
- Generate the final report from
resources/code-review-report-template.md.
Expected Inputs
Typical input is a feature directory, branch/diff context, or request such as:
- "Use $execute-review for tasks/prd-team-invitations."
- "Review the current git diff against the TechSpec and tasks."
- "Run a code review and create codereview.md."
If the feature context is unclear, inspect tasks/prd-* directories and the current git diff, then ask for clarification only when multiple plausible feature folders exist.
