/dev-review - Code Review

Skill Awareness: See skills/_registry.md for all available skills.

• Before: After /dev-coding implementation
• If issues: Fix with /dev-coding, then review again
• If major changes: Create CR via /debrief

Review code changes for quality, security, and adherence to standards.

When to Use

• After implementing a feature
• Before merging a PR
• To get feedback on approach
• To catch issues before production

Usage