brdohman/review-cycle
.claude/skills/workflow/review-cycle/SKILL.md
Canonical review cycle state machine, transition rules, and comment templates for all workflow stages. Use when advancing workflow state or writing review comments.
$ install --global
skillsauthnpx skillsauth add brdohman/agile-maestro review-cycleInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 7:20 PM7.2s1 file scanned
SKILL.md
- name:
- review-cycle
- description:
- Canonical review cycle state machine, transition rules, and comment templates for all workflow stages. Use when advancing workflow state or writing review comments.
- user-invocable:
- false
Review Cycle Reference
State Machine
For the complete state machine, field definitions, and lifecycle diagrams, see
.claude/docs/WORKFLOW-STATE.md.
Key rule: ANY rejection at ANY stage → Dev fixes → restart at code-review (full cycle restarts).
Comment Templates by Stage
STARTING (Dev claiming task)
STARTING: [brief plan]. Expected files: [list].
Type: note
TASK COMPLETED (Dev finishing task — NO review fields on task)
TASK COMPLETE
**Files changed:** [list]
**Checklist completed:** [x] each item
**Local checks verified:** [x] each check
**Completion signal met:** [how]
Type: implementation
READY FOR CODE REVIEW (Dev submitting story)
READY FOR CODE REVIEW
**Tasks completed:** [x] each task
**All files changed:** [consolidated list]
**Testing done:** [summary]
Type: handoff
CODE REVIEW PASSED / QA PASSED / PRODUCT REVIEW PASSED
[STAGE] PASSED
**What was checked:** [x] checklist items
**Notes:** [observations]
Type: review
REJECTED (any stage)
REJECTED - [STAGE]
**Issues found:**
1. **[title]** — Description, expected, actual, severity
**Next action:** Dev to fix and resubmit for code-review.
Type: rejection (uses trackable format with resolved, resolved_by, resolved_at)
FIXED AND RESUBMITTED (Dev after rejection)
FIXED AND RESUBMITTED
**Issues addressed:**
- [issue]: [how fixed]
**Verification evidence:** [test output, behavior diff]
Type: fix
Related Skills
brdohman/xctest-patterns
testing
VerifiedTrustedCommunity
XCTest patterns for macOS Swift apps. Unit tests, async tests, Core Data tests, mock patterns, and assertion reference. Use when writing or reviewing tests.
2SKILL.mdUpdated Apr 16, 2026
brdohman/workflow-state
tools
VerifiedTrustedCommunity
How to transition workflow state between review stages. Rules for setting review_stage and review_result fields on Stories and Epics.
2SKILL.mdUpdated Apr 16, 2026
brdohman/workflow-comments
documentation
VerifiedTrustedCommunity
Comment structure and rules for task workflow updates. Use when adding any comment to a task during implementation, review, or fix cycles.
2SKILL.mdUpdated Apr 16, 2026
brdohman/validate-task
testing
VerifiedTrustedCommunity
Validate task/story/epic/bug/techdebt metadata against schema v2.0. Run after TaskCreate or TaskUpdate to verify compliance. Returns pass/fail with actionable details.
2SKILL.mdUpdated Apr 16, 2026