Diagnose

Diagnose is a Quality skill for Claude Code, published by pedrohcgs in claude-code-my-workflow.

1.5K stars2.9K forkson pedrohcgs/claude-code-my-workflowAdded 2026/08/19+1% in starsRepository updated 2026/06/10

academic-writingcausal-inferenceclaude-codeclaude-code-skillseconometricseconomicslatexquartoreproducible-researchresearch-workflow

Install in seconds

Install Diagnose

Copy Diagnose into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/pedrohcgs/claude-code-my-workflow/tree/main/.claude/skills/diagnose ~/.claude/skills/diagnose

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/pedrohcgs/claude-code-my-workflow.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: .claude/skills/diagnose/SKILL.md in pedrohcgs/claude-code-my-workflow
Installs to: ~/.claude/skills/diagnose
Collection: One of 25 skills cataloged from this repository
Category: Quality — 1354 skills

What Diagnose does

Diagnose root-causes a failing or wrong empirical result with a disciplined reproduce → minimise → hypothesise → instrument → fix loop, instead of guessing-and-poking. Use when a regression is wrong, a number changed, a script errors, a result won't reproduce, or an estimate looks wrong.

Diagnose is cataloged under Quality on DirSkills. Diagnose comes from a repository tagged academic-writing, causal-inference, claude-code, claude-code-skills and econometrics.

Documentation

README

Excerpt

/diagnose — Root-Cause a Wrong or Failing Result

Find why an analysis errors, returns the wrong number, or won't reconcile — with a structured debugging loop rather than scattershot edits. Adapted from the diagnose pattern in mattpocock/skills, reshaped for empirical research code where the bug is usually a silent wrong number, not a crash.

The discipline: never edit before you can reproduce, and never fix before you can explain. A guessed fix that makes the symptom disappear without a named root cause is how a wrong number gets laundered into a published table.

When to use

This is the opening of the README. Read the full README on GitHub.

Commands Diagnose provides

Slash commands named in this skill’s SKILL.md, listed in the order they first appear.

/diagnose
/audit-reproducibility
/review-r
/capture-environment
/commit

Frequently asked about Diagnose

What else does pedrohcgs publish alongside Diagnose?
Diagnose is one of 25 skills that DirSkills catalogs from pedrohcgs/claude-code-my-workflow, the repository it ships in. Its siblings there include Audit Reproducibility, Capture Environment and Checkpoint. Each one is a separate skill with its own page in this directory, installs the same way Diagnose does, and is maintained by pedrohcgs in that same repository. The rest of the collection is listed on the pedrohcgs/claude-code-my-workflow page.
How does Diagnose compare to other Quality skills?
Diagnose ranks #647 by stars among the 1354 Quality skills in this catalog. The most-starred ones next to it are Benchmark, Benchmark Optimization Loop and API Design Patterns. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Diagnose against them. Open each page to compare what they document and how they install.