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 diagnose environment, tooling, and Agent Powerups setup problems.
> /plugin marketplace add yeaight7/agent-powerups
Use to diagnose environment, tooling, and Agent Powerups setup problems.
Steps:
1. Check required commands: `node --version`, `npx --version`, `python --version`, `git --version`, `apx --version`. 2. Run: `apx list` — confirm skills and commands are discoverable. 3. Run: `apx validate catalog` — should exit 0. 4. Run: `apx validate skills` — should exit 0. 5. Check MCP configs: `apx mcp check <name>` for each active config. 6. Check required env vars are set (names only — do not print values). 7. Run `git status --short` to check for stale generated assets. 8. Report blockers first, then non-blocking issues.
Do not install, modify, or configure anything unless explicitly asked.
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 turn a spec or user request into working, tested code.
Use to check MCP server prerequisites before activating or using a server.
Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.