bug-check
CommandRun automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
Use before starting any non-trivial task.
> /plugin marketplace add yeaight7/agent-powerups
Use before starting any non-trivial task.
Steps:
1. Re-read the user request in full. Identify the goal, constraints, and what "done" means. 2. Map affected areas: run `git status --short` and `apx list` to see what exists. 3. List the files most likely to change. For each, read its current state with the Read tool. 4. Write a numbered step list — small enough that each step is one logical change. 5. Identify risks: external dependencies, breaking changes, missing context. 6. Present the plan to the user and wait for approval before implementing.
Do not write code or modify files during planning.
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.