bug-check
Run automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
Use when a bug needs systematic diagnosis before a fix is attempted.
> /plugin marketplace add yeaight7/agent-powerupsHow it fires
How this command gets triggered: by you, by Claude, or both.
/debugContext preview
What this command does when you run it.
Use when a bug needs systematic diagnosis before a fix is attempted.
Use when a bug needs systematic diagnosis before a fix is attempted.
Steps:
1. Reproduce the failure. Run the smallest command or test that triggers it. 2. Read the error output in full. Identify the exact file and line. 3. Read the relevant source. Understand what the code was supposed to do. 4. Form one specific hypothesis: what is wrong and why. 5. Verify the hypothesis with a targeted test or log — do not fix yet. 6. Apply the minimal fix that addresses the root cause. 7. Re-run the original reproduction step. Confirm the failure is gone. 8. Run the full test suite to check for regressions: `npm test`.
Do not apply speculative fixes. One hypothesis, one verification, one fix.
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
Run automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
Use when a build, type check, or test suite is failing and needs to be unblocked with a minimal change.
Use to check MCP server prerequisites before activating or using a server.