bug-check
CommandRun automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
Use to perform a structured code review before merging or handing off.
> /plugin marketplace add yeaight7/agent-powerups
Use to perform a structured code review before merging or handing off.
Steps:
1. Get the diff: `git diff main...HEAD` or `gh pr diff <PR-number>`. 2. Read each changed file in full — don't review from diff context alone. 3. Check correctness: does the logic match the stated intent? Are there edge cases unhandled? 4. Check tests: are new behaviors covered? Run `npm test` (or the repo's test command) if tests changed. 5. Check style: naming, duplication, comment hygiene. 6. Run `apx validate catalog` if catalog.json or asset files changed. 7. Write findings as a short list: what's correct, what needs fixing, what's optional.
Do not commit, push, or approve PRs from within this workflow.
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.