- New skill: sprint-lifecycle.md defines states, transitions, and check protocol - All sprint commands now check and set lifecycle state - States tracked in milestone description metadata (Sprint/Planning, Sprint/Executing, Sprint/Reviewing) - Out-of-order calls produce warnings with guidance - --force override available for all lifecycle checks - Added Sprint/* labels to label taxonomy documentation Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2.0 KiB
2.0 KiB
description, agent
| description | agent |
|---|---|
| Pre-sprint-close code quality review | code-reviewer |
Code Review for Sprint Close
Skills Required
- skills/review-checklist.md
- skills/sprint-lifecycle.md
Purpose
Review recent code changes for quality issues before closing the sprint.
Invocation
Run /review before /sprint-close to catch issues.
Workflow
- Check Lifecycle State - Execute
skills/sprint-lifecycle.mdcheck protocol. ExpectSprint/Executing. SetSprint/Reviewingafter review begins. Warn if in wrong state (allow with--force). - Determine Scope - Sprint files or recent commits (
git diff --name-only HEAD~5) - Read Files - Use Read tool for each file in scope
- Scan for Patterns - Check each category from review checklist
- Compile Findings - Group by severity (Critical, Warning, Recommendation)
- Report Verdict - READY / NEEDS ATTENTION / BLOCK
Review Categories
See skills/review-checklist.md for complete patterns:
- Debug artifacts (TODO, console.log, commented code)
- Code quality (long functions, deep nesting, duplication)
- Security (hardcoded secrets, SQL injection, disabled SSL)
- Error handling (bare except, swallowed exceptions)
DO NOT
- Rewrite or refactor code automatically
- Make changes without explicit approval
- Review files outside sprint/change scope
- Spend excessive time on style issues
Visual Output
╔══════════════════════════════════════════════════════════════════╗
║ 📋 PROJMAN ║
║ 🏁 CLOSING ║
║ Code Review ║
╚══════════════════════════════════════════════════════════════════╝