bug-check
CommandRun automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
Draft a step-by-step refactoring strategy for complex code changes to ensure behavior is preserved.
> /plugin marketplace add yeaight7/agent-powerups
description: Draft a step-by-step refactoring strategy for complex code changes to ensure behavior is preserved.
You are a senior software architect. Draft a comprehensive, step-by-step plan for refactoring the requested code or architecture.
`$ARGUMENTS`
1. **Goal Definition:** Clarify the end state of the refactoring (e.g., decoupling a monolith, upgrading a core framework, extracting a service). 2. **Safety Net:** Define the testing strategy required before any code is modified. 3. **Execution Phases:** Break the refactoring into isolated, verifiable phases. Each phase must leave the system in a deployable state. 4. **Rollback Strategy:** Provide a clear rollback or fallback mechanism for each phase in case of unexpected failures.
Do not write the final refactored code yet. Focus exclusively on delivering a structured, low-risk execution plan that a developer can follow systematically.
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
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 when a bug needs systematic diagnosis before a fix is attempted.
Use to diagnose environment, tooling, and Agent Powerups setup problems.
Use to turn a spec or user request into working, tested code.
Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.