30-SECOND BRIEF
What it does—and when it fits
Diagnosing Bugs is an evidence-first loop for difficult defects and performance regressions. It reads project context and ADRs, redacts secrets from every command and artifact, first builds a tight deterministic pass/fail reproduction, then uses hypotheses, bisection, traces, differential checks, or human-in-the-loop evidence before fixing and adding a regression test.
INSTALL BY AGENT
Choose your Agent
Paths come from official Agent docs or the universal installer behind skills.sh. Compatibility still follows this Skill's record.
.claude/skills/diagnosing-bugs/~/.claude/skills/diagnosing-bugs/Use project scope for team sharing and personal scope across repositories. The installer defaults to project scope; add -g for personal scope.
npx skills add mattpocock/skills --skill diagnosing-bugs --agent claude-codeClaude Code discovers custom Skill folders automatically at project or personal scope.
View path evidence ↗TYPICAL WORKFLOW
A practical workflow
Build a deterministic reproducer
Turn a vague report into a small test, fixture, request, trace, or harness.
Bisect the cause
Reduce the search space with explicit hypotheses and controlled comparisons.
Lock in the fix
Verify the repair in the tight loop and add a regression test.
THE TRADEOFFS
Advantages and tradeoffs
Notable strengths
- This profile is manually organized around the current upstream SKILL.md workflow.
- The capability boundary remains explicitly tied to mattpocock/skills.
- Core uses, limitations, and risks are separated for pre-install review.
Limitations
- It requires a repeatable pass/fail signal; intermittent production-only failures may need observability or human evidence first.
- Diagnosis can identify a cause without authorizing invasive production changes or broad refactoring.
BEST FIT
Who it is for
Engineers investigating hard-to-reproduce bugs
Teams diagnosing performance regressions
BEFORE YOU USE IT
Risks to review before use
Secrets captured in diagnostic evidence
Requests, traces, screenshots, and logs can contain tokens, credentials, personal data, or production payloads. Redact before capture, minimize retention, and restrict access to every diagnostic artifact.
Upstream instruction drift
Behavior can change with upstream updates. Record the commit used for important workflows and review updates before adoption.
SECURITY
What the permission profile means
- Declared access remains governed by the current upstream SKILL.md and runtime requests.
- Treat repository files, web content, and tool output as untrusted input.
- SkillSignal has not independently executed or security-audited this package; external skills.sh labels are not SkillSignal certification.
Not a security certification. External ratings are attributed references. SkillSignal has not independently executed or security-reviewed this Skill.
INSIDE THE PACKAGE
Indexed files
TAGS
Manually expanded from the current upstream SKILL.md and linked source at mattpocock/skills, checked 2026-08-20. This is an original summary, not an execution result or security certification.