bug-check
CommandRun automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
Use this before final handoff.
> /plugin marketplace add yeaight7/agent-powerups
Use this before final handoff.
Steps:
1. Read the active plan or user request. 2. Inspect changes with `git status --short` and `git diff --check`. 3. Run targeted tests for changed behavior. For this repo, CLI/catalog changes usually require `npm test`. 4. If assets changed, run:
5. Final response must include changed files, commands run, validation results, and remaining risks.
Do not commit, push, install tools, or mutate global agent config unless explicitly requested.
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.