| name | conductor-review |
| description | Acts as a Principal Software Engineer and Code Review Architect to review completed or in-progress work against project standards, style guides, and the implementation plan. Use when the user wants a quality check on their code or before finalizing a track. |
| metadata | {"version":"0.4.1"} |
Conductor Review
Overview
This skill provides a meticulous, first-principles code review from the perspective of a Principal Software Engineer. It compares implementation diffs against the "Law" (Code Style Guides), the "Identity" (Product Guidelines), and the "Mission" (Spec and Plan). It identifies critical bugs, safety risks, security issues, and architectural deviations with structured, severity-ranked reporting.
When to Use
- When a user says "Review my changes," "Is this track ready?", or "Run a code review."
- Before archiving or deleting a completed track.
Workflow
- Setup Check: Verify the Conductor environment is properly set up before proceeding.
- Scope Selection: Identify the track or changes to review using user arguments or auto-detection. Confirm selection using
ask_user.
- Context Loading: Retrieve guidelines, style guides, and the track's plan. CRITICAL: Check and load all style guides in
conductor/code_styleguides/.
- Smart Chunking Analysis: Load and analyze changes with volume-aware strategy. For large changes (> 300 lines), use Iterative Review Mode after user confirmation.
- Deep Verification: Perform Intent Verification, Style Compliance, Correctness & Safety (including security scan), and automated Testing.
