Diagnose
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
Install
npx skills add javimosch/supercli --skill diagnosegit clone --depth 1 https://github.com/javimosch/supercli.git /tmp/supercli
mkdir -p ~/.claude/skills
cp -r /tmp/supercli/.agents/skills/diagnose ~/.claude/skills/diagnosePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Diagnose A discipline for hard bugs. Skip phases only when explicitly justified. When exploring the codebase, use the project's domain glossary to get a clear mental model of the relevant modules, and check ADRs in the area you're touching. ## Phase 1 — Build a feedback loop **This is the skill.** Everything else is mechanical. If you have a fast, deterministic, agent-runnable pass/fail signal for the bug, you will find the cause — bisection, hypothesis-testing, and instrumentation all just consume that signal. If you don't have one, no amount of staring at code will save you. Spend disproportionate effort here. **Be aggressive. Be creative. Refuse to give up.** ### Ways to construct one — try them in roughly this order 1. **Failing test** at whatever seam reaches the bug — unit, integration, e2e. 2. **Curl / HTTP script** against a running dev server. 3. **CLI invocation** with a fixture input, diffing stdout against a known-good snapshot. 4. **Headless browser script** (Playwright / Puppeteer) — drives the UI, asserts on DOM/console/network. 5. **Replay a captured trace.** Save a real network request / payload / event log to disk; replay it through the code path in isolation. 6. **Throwaway harness.** Spin up a minimal subset of the system (one service, mocked deps) that exercises the bug code path with a single function call. 7. **Property / fuzz loop.** If the bug is "sometimes wrong output", run 1000 random inputs and look for the failure mode.
Details
- Skill name
diagnose- Repository
- javimosch/supercli
- Path
.agents/skills/diagnose/SKILL.md- License
- MIT
- Repo updated
- 2 November 2026
- Listed in
- heilcheng/awesome-agent-skills
FAQ
What does the Diagnose skill do?
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
How do I install the Diagnose skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add javimosch/supercli --skill diagnose. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Diagnose popular?
It lives in javimosch/supercli, which has 57 GitHub stars and 5 forks, and is included in 1 curated skill list.
Related skills
100 Exercises to Learn Rust
57javimosch/supercli
Use this skill when the user wants to use 100-exercises-to-learn-rust.
2to3
57javimosch/supercli
Use this skill when the user wants to use 2to3, cli tool: 2to3.
2to3 2.7
57javimosch/supercli
Use this skill when the user wants to use 2to3-2.7, cli tool: 2to3-2.7.
Equa11y
57javimosch/supercli
Use this skill when the user wants to stream-lined command line tool for running accessibility testing with axe-core and puppeteer.
CRLF Injection Scanner
57javimosch/supercli
Use this skill when the user wants to command line tool for testing crlf injection on a list of domains.
Galaxy
57javimosch/supercli
Use this skill when the user wants to use Galaxy for 一个想让你测试加密流量像测试明文一样简单高效的 Burp 插件。 A Burp plugin that makes testing encrypted traf.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.