/diagnose-failure
Systematically analyze a reported error, stack trace, or failure state to identify the root cause and propose a fix.
$ npx -y skills add yeaight7/agent-powerups --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/diagnose-failure
Context preview
What this command does when you run it.
Systematically analyze a reported error, stack trace, or failure state to identify the root cause and propose a fix.
Command definition
diagnose-failure.mddescription: Systematically analyze a reported error, stack trace, or failure state to identify the root cause and propose a fix.
Diagnose Failure
You are an expert in debugging and failure analysis. Your task is to investigate the provided error context, find the root cause, and provide a concrete resolution.
Context
`$ARGUMENTS`
Diagnostic Steps
1. **Analyze Symptoms:** Review the provided logs, stack traces, or unexpected outputs. 2. **Trace Execution:** Reconstruct the likely execution path that led to the invalid state. 3. **Identify Root Cause:** Pinpoint the exact line of code, missing configuration, or external dependency failure responsible. 4. **Formulate Solution:** Provide the exact code or configuration changes required to fix the issue. 5. **Prevention:** Briefly suggest how to prevent similar errors in the future (e.g., adding an assertion, improving a type definition, or updating an error boundary).
Be concise and focus on actionable solutions. Do not generate generic debugging advice; tailor your response to the exact failure provided.
Curated power-ups for coding agents: skills, slash commands, MCP configs, hooks, AGENTS.md templates, and workflows for serious software engineering. Claude Code, Codex, Antigravity CLI, Cursor and more
Repo: yeaight7/agent-powerups
Other commands on agent-powerups.
- /bug-check
Run automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
Open command - /build-fix
Use when a build, type check, or test suite is failing and needs to be unblocked with a minimal change.
Open command - /debug
Use when a bug needs systematic diagnosis before a fix is attempted.
Open command - /doctor
Use to diagnose environment, tooling, and Agent Powerups setup problems.
Open command - /implement
Use to turn a spec or user request into working, tested code.
Open command - /mcp-check
Use to check MCP server prerequisites before activating or using a server.
Open command