Four-phase root cause analysis for bug investigation. Activates when debugging unexpected behavior, failing tests, or production issues — follows reproduce, isolate, analyze, fix with defense-in-depth. Uses condition-based waiting instead of arbitrary delays. Available anytime, not tied to the inner loop sequence.
Conducts structured four-phase root cause analysis for debugging unexpected behavior or failing tests.
/plugin marketplace add brite-nites/brite-claude-plugins/plugin install workflows@brite-claude-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
You are investigating a bug using a structured four-phase process. The goal is to find and fix the root cause, not just suppress the symptom.
Before anything else, reliably reproduce the problem.
## Reproduction
Steps: [exact steps]
Expected: [what should happen]
Actual: [what happens instead]
Frequency: [always / intermittent / specific conditions]
Environment: [OS, Node version, browser, etc.]
Narrow down where the bug lives.
git bisect start, git bisect bad, git bisect good [known-good-commit]console.log everywhere)assert statements at key points to catch violations## Isolation
Location: [file:line or module]
Narrowed from: [original scope] → [isolated location]
Method: [how you narrowed it down]
Understand why the bug exists, not just where.
After identifying the root cause, ask:
## Root Cause
Cause: [precise description]
Category: [logic / state / integration / environment / missing handling]
Why it wasn't caught: [gap in testing, types, or review]
Related risks: [other places with similar patterns]
Fix the root cause and prevent regression.
Beyond the immediate fix, consider:
If the bug involves timing or async behavior:
sleep 5, setTimeout(5000))sleep 2 && check_result, use i=0; while ! check_result && [ $i -lt 100 ]; do sleep 0.1; i=$((i+1)); done## Fix
Change: [what was changed and why]
Files: [list of modified files]
Test: [the regression test that was added]
Defense: [additional protective measures added]
Related fixes: [similar patterns fixed elsewhere, or "none"]
Present the full debugging report:
## Debugging Complete: [Brief title]
**Bug**: [one-line description]
**Root cause**: [one-line root cause]
**Fix**: [one-line fix description]
**Reproduction** → **Isolation** → **Analysis** → **Fix**
[Link to each section above]
**Regression test**: [test name and how to run it]
**Tests**: All passing
**Build**: Clean
**Compound learning**: [If this revealed a pattern, it should be captured via compound-learnings]
console.log — add targeted, informative loggingCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.