Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
Use after fixing a bug to generate a blameless post-mortem summary for human review.
npx claudepluginhub yeaight7/agent-powerups --plugin debugging-diagnosticsHow this skill is triggered — by the user, by Claude, or both
Slash command
/debugging-diagnostics:incident-readoutThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
When a complex debugging session ends, you must produce an incident readout. This prevents knowledge loss and helps humans review the fix quickly.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Explores codebases via GitNexus: discover repos, query execution flows, trace processes, inspect symbol callers/callees, and review architecture.
Share bugs, ideas, or general feedback.
When a complex debugging session ends, you must produce an incident readout. This prevents knowledge loss and helps humans review the fix quickly.
Output an incident-readout.md (or print to terminal) using this structure:
What was reported? (1-2 sentences)
What was the actual underlying technical reason for the failure? Be highly specific about the exact line of code, assumption, or state that failed.
What did we change to fix it? Provide a high-level summary of the structural change, not just a diff.
How do we ensure this never happens again? (e.g., "Added test case X", "Refactored module Y to be strongly typed").