red-flags

1

codybrom

Scans code for common design smells across structure, boundaries, documentation, naming, and process. Use when the user asks for a red flags scan, when reviewing a PR, evaluating unfamiliar code, or when code feels wrong but the problem is unclear. Produces a structured report with status, violated principle, and candidate fix for each flag.

diagnose

1

codybrom

Routes a vague symptom or complaint to the most relevant Clairvoyance skill via a decision tree. Use when someone describes a problem but doesn't know which skill to reach for. Not for running a comprehensive review (use design-review) or scanning a checklist (use red-flags).

design-review

1

codybrom

Orchestrates a structured design review by running existing skills in a diagnostic funnel, from complexity triage through structural, interface, and surface checks to a full red-flags sweep. Use when reviewing a file, module or PR for overall design quality and you want a comprehensive, prioritized assessment rather than a single-lens check. Not for applying one specific lens (use that skill directly) or for evolutionary analysis of how code changed over time (use code-evolution).