recipe-front-review

Context: Post-implementation quality assurance for React/TypeScript frontend

Execution Method

• Compliance validation → performed by code-reviewer
• Rule analysis → performed by rule-advisor
• Fix implementation → performed by task-executor-frontend
• Quality checks → performed by quality-fixer-frontend
• Re-validation → performed by code-reviewer

Orchestrator invokes sub-agents and passes structured JSON between them.

Design Doc (uses most recent if omitted): $ARGUMENTS

Think deeply Understand the essence of compliance validation and execute:

Execution Flow

1. Prerequisite Check

# Identify Design Doc
ls docs/design/*.md | grep -v template | tail -1

# Check implementation files
git diff --name-only main...HEAD

2. Execute code-reviewer

Validate Design Doc compliance:

• Acceptance criteria fulfillment
• Code quality check
• Implementation completeness assessment

3. Verdict and Response

Criteria (considering project stage):

• Prototype: Pass at 70%+
• Production: 90%+ recommended
• Critical items (security, etc.): Required regardless of rate

Compliance-based response:

For low compliance (production <90%):

Validation Result: [X]% compliance
Unfulfilled items:
- [item list]

Execute fixes? (y/n):

If user selects y:

Pre-fix Metacognition

Required: rule-advisor → TaskCreate → task-executor-frontend → quality-fixer-frontend

1. Execute rule-advisor: Understand fix essence (symptomatic treatment vs root solution)
2. Register tasks using TaskCreate: Register work steps. Always include: first "Confirm skill constraints", final "Verify skill fidelity". Create task file following task template (see documentation-criteria skill) → docs/plans/tasks/review-fixes-YYYYMMDD.md
3. Execute task-executor-frontend: Staged auto-fixes (stops at 5 files)
4. Execute quality-fixer-frontend: Confirm quality gate passage
5. Re-validate: Measure improvement with code-reviewer

4. Final Report

Initial compliance: [X]%
Final compliance: [Y]% (if fixes executed)
Improvement: [Y-X]%

Remaining issues:
- [items requiring manual intervention]

Auto-fixable Items

• Simple unimplemented acceptance criteria
• Error handling additions
• Contract definition fixes
• Function splitting (length/complexity improvements)

Non-fixable Items

• Fundamental business logic changes
• Architecture-level modifications
• Design Doc deficiencies

Scope: Design Doc compliance validation and auto-fixes.