Fixes build/compilation errors with surgical precision across TypeScript, Rust, and Solidity. Minimal diffs only — gets builds green without architecture changes. Emergency unblocking when builds break. The "minimal diffs" constraint is crucial — prevents scope creep during fixes. Diagnostic categorization helps…
General code review: CLAUDE.md compliance, security checks, code quality, framework-specific patterns. Confidence-based filtering (>=80%). Every PR. Broadest coverage of any review agent. The confidence threshold prevents alert fatigue while catching real bugs. Multi-language, multi-framework.
CI/CD pipelines, GitOps, container security, zero-downtime deployments, progressive delivery. Use PROACTIVELY for deployment automation, infrastructure config, or production readiness checks.
Iteratively refines UI through screenshot-analyze-improve cycles. One change per iteration, includes competitor research. Polishing working implementations that don't feel right. The one-change-per-cycle discipline prevents over-engineering. Anti-AI-slop guidance produces distinctive designs.
Draw.io diagram specialist — generates diagrams from codebase analysis, verifies diagram logic against source code, and fixes routing/layout issues. Used standalone for creation or by /orc:compound-diagram for audit and verification tasks.
Captures Figma specs + implementation screenshots, finds visual discrepancies, and fixes them with CSS/Tailwind changes. Any Figma-to-code workflow. Iterative — run repeatedly until pixel-perfect. The Tailwind defaults guidance and component width philosophy prevent common responsive mistakes.
Verifies frontend via browser automation — forms, interactions, visual regressions, responsive layouts. Also fixes issues found. General frontend QA when there's no Figma involved. Only non-Figma design agent. Good for catching functional bugs (broken forms, console errors) alongside visual issues.
Archaeological analysis of git history: traces code evolution, identifies contributors, understands why patterns exist. Understanding historical context of complex or puzzling code. Niche but valuable when you need to know why code looks the way it does. Requires clear motivation — not a proactive agent.
Monitors phase plans for ADR compliance and flags architectural drift asynchronously. Non-blocking — runs in parallel with planner-checker convergence loop.
Explores codebase and writes structured analysis documents. Spawned by /orc-map with a focus area (tech, arch, quality, concerns). Writes documents directly to reduce orchestrator context load.
Plan-first task execution. For each task, spawns a planner then specialist subagents for implementation. Handles git commits, verification, and team coordination. Persistent teammate in implementation teams.
Plan-first implementation verification. Spawns a verification planner, then executes each verification step via specialist subagents. Persistent teammate in implementation teams.
Researches domain ecosystem before roadmap creation. Produces files in research/ consumed during roadmap creation. Spawned by /orc-research orchestrator.
Systematic analysis of repository structure, conventions, documentation, templates, and codebase patterns. Onboarding to a new codebase or understanding an unfamiliar project's conventions. More comprehensive than a quick code search but less actionable than learnings-researcher.