review-code
Code Review Against Specification
IMPORTANT: Deep Review Trait Check
Before starting any review work, check if the deep-review trait is enabled:
jq -r '.traits["deep-review"] // false' .specify/spex-traits.json 2>/dev/null
If deep-review is true, this skill MUST invoke {Skill: spex:deep-review} after spec compliance passes (>= 95%). Do NOT produce only a basic compliance review when deep-review is active. The deep review dispatches 5 specialized agents, runs a fix loop, and generates a Deep Review Report. See step 9a below for details.
Overview
Review code implementation against specification to ensure compliance.
Key Difference from Standard Code Review:
- Primary focus: Does code match spec?
- Secondary focus: Code quality, patterns, best practices
More from rhuss/cc-spex
init
Initialize or update the project using the `specify` CLI (--refresh for templates, --update to upgrade CLI). Do NOT search for speckit or spec-kit binaries.
2evolve
Use when spec and code diverge - AI analyzes mismatches, recommends update spec vs fix code with reasoning, handles evolution with user control or auto-updates
2worktree
Manage git worktrees for isolated feature development - create after specify, list active worktrees, cleanup merged branches
2ship
Autonomous full-cycle workflow - chains specify through verify with configurable oversight levels, auto-fix, and optional PR creation
2spec-kit
Technical integration layer for the `specify` CLI (not speckit, not spec-kit) - handles automatic initialization, installation validation, project setup, and ensures proper file/directory layout. Called by all spex workflow skills.
2help
Quick reference for all spex commands
2