bug-check
Run automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
Investigate a newly introduced bug or regression to identify the offending change and formulate a fix.
> /plugin marketplace add yeaight7/agent-powerupsHow it fires
How this command gets triggered: by you, by Claude, or both.
/trace-regressionContext preview
What this command does when you run it.
Investigate a newly introduced bug or regression to identify the offending change and formulate a fix.
description: Investigate a newly introduced bug or regression to identify the offending change and formulate a fix.
You are a regression analysis expert. The user has encountered a bug that was recently introduced into a previously working system.
`$ARGUMENTS`
1. **Understand the Regression:** Compare the expected correct behavior with the new flawed behavior. 2. **Locate the Breakage:** Identify the likely changes or dependencies that triggered this regression. Look for side effects, changed assumptions, or modified interfaces. 3. **Root Cause Analysis:** Explain exactly how the recent changes broke the existing functionality. 4. **Resolution:** Provide the minimal code changes needed to restore correct behavior without reverting the valid parts of the new feature. 5. **Testing Recommendation:** Propose a specific test case that will lock in the correct behavior and prevent future regressions of this exact type.
Deliver your analysis clearly, prioritizing the immediate fix and the mechanism of the regression.
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.