Individual skill

diagnose

0upvotes

Use when the user reports a hard bug, unexpected failure, or performance regression that needs root-cause analysis.

skills/diagnose/SKILL.md

Read pinned source

Source commit b3dd7adf7da9200bbc81c4e300905e9e932d538c

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: No
Observed behavior: Not checked yet
Last checked: Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 15
Repository last updated: Oct 27, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agent-harness Repository topic
agent-skills Repository topic
ai-agent Repository topic
claude-code Repository topic
claude-skills Repository topic
codex Repository topic
cursor Repository topic
devin Repository topic
mcp Repository topic
mcp-server Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 31,512 bytes
SKILL.mdcore · 31,512 bytes
SKILL.mdcore · 31,512 bytes
references/angular-debugging.mddoc · 4,584 bytes
references/condition-based-waiting.mddoc · 2,837 bytes
references/defense-in-depth.mddoc · 2,302 bytes
references/dotnet-debugging.mddoc · 5,697 bytes
references/python-debugging.mddoc · 5,007 bytes
references/react-debugging.mddoc · 4,643 bytes
references/root-cause-tracing.mddoc · 2,950 bytes
scripts/find-polluter.shruns · 2,265 bytes
scripts/hitl-loop.template.shruns · 1,316 bytes

Read excerpt


# Diagnose

A discipline for hard bugs and regressions. Skip phases only when explicitly justified. All questions and findings reported to the user must be in **Portuguese (pt-BR)**.

When exploring the codebase, use the project's domain glossary from `.claude/CONTEXT.md` (if it exists) to get a clear mental model of the relevant modules, and check `docs/architecture/` for decisions and ADRs in the area you are touching.

**Re-validation loop**: after every hypothesis, fix, or change, re-run the reproduction and the regression checks before declaring the bug resolved.

**Iron rule:** NO FIXES WITHOUT A RED LOOP AND A CONFIRMED ROOT CAUSE. A change made before Phase 1 produced a red signal and Phase 4 confirmed a hypothesis is a guess — and guessing under pressure is how one bug becomes three. This holds ESPECIALLY under time pressure, when the bug "looks simple", and after a previous fix already failed: those are exactly the moments the process pays off. Violating the letter of this process is violating the spirit of debugging.

## Pipeline

```text
Phase 0  Frame the bug          → symptom, expected vs actual, env, frequency, scope