Route vague software design symptoms to the most relevant analysis skill.
npx skills add https://github.com/codybrom/clairvoyance --skill diagnose-codybrom
Please help me install this Agent Skill. Skill: diagnose Source: https://github.com/codybrom/clairvoyance/tree/main/skills/diagnose Command: npx skills add https://github.com/codybrom/clairvoyance --skill diagnose-codybrom
Diagnose helps developers turn vague software design symptoms into a focused next step instead of guessing which review or analysis method to use.
Ask the diagnose skill to identify the best Clairvoyance review for a description such as “simple changes require edits in many files.”
High-intent search queries and answers about installing and using this skill.
Diagnosing vague software design symptoms involves classifying complaints like change amplification or awkward interfaces to route them to the most relevant code review skill for targeted refactoring and technical debt reduction.
The best way to analyze technical debt from scattered changes is to classify the symptom as change amplification, which routes the codebase to a structural priority review that reads the code paths and identifies root-cause design flaws.
Handling a code review for unclear names and redundant layers requires classifying these structural and documentation concerns separately, prioritizing the structural design flaws before addressing the documentation or routing to a fallback scan.
Yes, symptom routing can find the cause of excessive errors and awkward interfaces by classifying these specific complaints, optionally reading the referenced code paths with Read and Grep, and matching them to the correct analysis skill.
When vague technical debt complaints do not match a known software design pattern, the diagnosis applies a fallback routing mechanism that sends the unmatched symptoms to a red-flags scan for a systematic design-smell detection.
jimmymalhanClassify incidents into predefined categories and route them in a diagnostic pipeline.
sjmyuanGenerate step-by-step TDD-based refactoring plans for code cleanup and architecture improvements.
sncollectiveIdentify code duplication, complexity, and pattern drift in a codebase.
joshsymondsReview tasks against an 8-category checklist and update them with measurable criteria.
