mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-03-10 17:11:04 +08:00
- Introduced a comprehensive template for generating epics and stories in Phase 5, including an index and individual epic files. - Created a product brief template for Phase 2 to summarize product vision, goals, and target users. - Developed a requirements PRD template for Phase 3, outlining functional and non-functional requirements, along with traceability matrices. feat: Implement tech debt roles for assessment, execution, planning, scanning, validation, and analysis - Added roles for tech debt assessment, executor, planner, scanner, validator, and analyst, each with defined phases and processes for managing technical debt. - Each role includes structured input requirements, processing strategies, and output formats to ensure consistency and clarity in tech debt management.
983 B
983 B
Code Review
4-dimension code review for implementation quality.
Inputs
- Plan file (plan.json)
- Git diff or modified files list
- Test results (if available)
Dimensions
| Dimension | Critical Issues |
|---|---|
| Quality | Empty catch, any casts, @ts-ignore, console.log |
| Security | Hardcoded secrets, SQL injection, eval/exec, innerHTML |
| Architecture | Circular deps, imports >2 levels deep, files >500 lines |
| Requirements | Missing core functionality, incomplete acceptance criteria |
Review Process
- Gather modified files from executor's state (team_msg get_state)
- Read each modified file
- Score per dimension (0-100%)
- Classify issues by severity (Critical/High/Medium/Low)
- Generate verdict (BLOCK/CONDITIONAL/APPROVE)
Output
Write review report to /artifacts/review-report.md:
- Per-dimension scores
- Issue list with file:line references
- Verdict with justification
- Recommendations (if CONDITIONAL)