Skip to main content
skill CX Codex

diagnosing-root-causes — Claude Code skill: trace failures

The diagnosing-root-causes skill traces bugs, regressions, and CI/CD failures from supplied evidence, then produces a reviewed root-cause report. Use it when a problem report needs investigation rather than guesswork.

no license 122 installs ★ 3 updated 2026-10-25

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add b-mendoza/agent-skills --skill diagnosing-root-causes -a claude-code
Open on GitHub

What diagnosing-root-causes does

Give the skill an issue description and materials such as logs, repository paths, CI output, or a commit range. It classifies the report, asks for clarification when needed, then routes evidence gathering, causal analysis, and report review to three subagents. The final conclusions are tied to supporting evidence.

The workflow follows a finite state machine. Investigation is read-only by default, and the skill never performs Tier C actions, even with approval; approval can produce a handoff for a person instead. That boundary matters if you expect the agent to change code or run a risky operation. When the environment has no subagent tool, the phases run in one context, so the report review is not independent.

Provide the problem and its supporting materials to start. Reproduction steps, environment details, and the issue source can add context. Reports end with ready, blocked, needs-validation, or escalated; early stops use needs-input or error.

What it helps with

  • trace an application crash from logs
  • investigate a regression after a code change
  • identify why a CI/CD pipeline fails
  • check whether a bug report has enough evidence
  • prepare a reviewable root-cause report

Example prompts for the agent

  • Investigate the application failure using logs/build-42.txt and separate confirmed findings from hypotheses.
  • Find why the CI/CD pipeline failed after the dependency update using the supplied logs and commit range.
  • Review this bug report and ask for the missing details needed to investigate it.

How to install diagnosing-root-causes

1Skills CLI (Vercel)

npx skills add b-mendoza/agent-skills --skill diagnosing-root-causes -a claude-code

2Manually: put the files in place

~/.claude/skills/diagnosing-root-causes/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/diagnosing-root-causes/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about diagnosing-root-causes

How do I install diagnosing-root-causes in Claude Code?

Run npx skills add b-mendoza/agent-skills --skill diagnosing-root-causes -a claude-code. The skill file is placed at ~/.claude/skills/diagnosing-root-causes/SKILL.md.

What does diagnosing-root-causes do?

It gathers evidence about a reported issue, delegates causal analysis, and checks the resulting report. It covers bugs, regressions, and CI/CD failures.

Can the skill apply a fix itself?

No. It stays read-only for its investigation and does not perform Tier C actions, even after approval. An approved action at that tier is packaged for human-supervised execution.

Similar skills

All skills for Testing and QA →

From the same set12

The whole set →
review-pull-request review-pull-request audits a single GitHub pull request across isolated stages, drafts a local Markdown report, and posts comments only when confirmed. CX Codex +1 161installs committing-scoped-changes committing-scoped-changes splits an explicit list of files or folders into separate git commits and leaves the rest of the working tree alone. CX Codex +1 153installs responding-to-pr-review-comments The responding-to-pr-review-comments skill gathers pull request comments, assesses the feedback, and drafts replies. With confirmation, it can post approved text to supported GitHub comment threads. CX Codex +1 144installs clarifying-assumptions clarifying-assumptions — a skill that runs the conversational layer for plan verification. Asks critical questions upfront or before individual tasks, delegates artifact analysis to subagents. CX Codex +1 129installs refactoring-code refactoring-code is a Claude Code skill that stages simplification refactors: approve the plan before edits, then check that behaviour stays the same. CX Codex +1 124installs rewriting-code-strictly rewriting-code-strictly is a Claude Code skill that rewrites Python, TypeScript/JavaScript, or Go with stricter typing and boundary checks. It runs on requests to harden code or align it with static analysis tools. CX Codex +1 122installs improving-test-suites improving-test-suites is a Claude Code skill that reviews test suites and focuses them on important behavior. It activates for requests to trim, rewrite, review, or strengthen tests. CX Codex +1 119installs planning-codebase-restructuring planning-codebase-restructuring is a Claude Code skill that maps a codebase and prepares a restructuring plan without changing files. It produces an evidence-backed report for a later implementation pass. CX Codex +1 100installs

Project sponsors

Companies that keep this analytics open