Harness Review
Review code against the project docs and Harness rules.
Read First
AGENTS.mddocs/ARCHITECTURE.mddocs/ADR.mddocs/PRD.mddocs/UI_GUIDE.mdif UI is involved
Review Focus
Prioritize:
- Regressions
- Spec mismatches
- Missing tests
- Security and data integrity risk
- Architecture drift
Process
- Identify the change set.
- Review the diff or changed files.
- Compare the result against project docs.
- Report findings first, ordered by severity.
When helpful, use:
codex review --uncommitted
or compare against a base branch with:
codex review --base main
Checklist
- Follows
AGENTS.mdguardrails - Matches
docs/ARCHITECTURE.md - Respects ADR decisions
- Supports PRD requirements
- Includes tests for new behavior
- Avoids banned UI patterns from
docs/UI_GUIDE.md
Output
- Findings first
- Then open questions or assumptions
- Then a short summary only if needed
If no findings remain, say that clearly and mention any residual test gap.
Source: soohy00/codex-harness-framework — distributed by TomeVault.