diagnose

Route vague software design symptoms to the most relevant analysis skill.

11|Updated Feb 25, 2026

Search Tags:#code review #refactoring #software design #technical debt #diagnosis #symptom routing

Ready to run

npx skills add https://github.com/codybrom/clairvoyance --skill diagnose-codybrom

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose helps developers turn vague software design symptoms into a focused next step instead of guessing which review or analysis method to use.

Core Features & Use Cases

Symptom routing: Maps complaints such as excessive errors, awkward interfaces, scattered changes, and redundant layers to the most relevant Clairvoyance skill.
Root-cause prioritization: Distinguishes structural, process, and documentation concerns, while identifying secondary matches for follow-up.
Code-aware diagnosis: Reads referenced code paths before routing when additional confirmation is needed.
Fallback coverage: Sends unmatched symptoms to red-flags for a systematic design-smell scan.

Quick Start

Ask the diagnose skill to identify the best Clairvoyance review for a description such as “simple changes require edits in many files.”

Frequently Asked Questions about diagnose

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I figure out which code review method to use for vague software design symptoms?▼

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.

What is the best way to analyze technical debt when simple changes require edits in many files?▼

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.

How do I handle a code review when the only symptom is unclear names and redundant layers?▼

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.

Can I use symptom routing to find the cause of excessive errors and awkward interfaces?▼

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.

What happens to vague technical debt complaints that do not match a known software design pattern?▼

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.