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 turn a spec or user request into working, tested code.
> /plugin marketplace add yeaight7/agent-powerups
Use to turn a spec or user request into working, tested code.
Steps:
1. Read the spec or request in full. If anything is ambiguous, ask before writing a single line. 2. Identify the files to create or modify. Read them first. 3. Write a failing test that captures the expected behavior. Confirm it fails. 4. Implement the minimum code that makes the test pass. No extras. 5. Run the full test suite: `npm test`. All tests must pass. 6. If assets were added or changed, run `apx validate catalog`. 7. Update any affected documentation or usage examples.
Do not add features beyond the spec. Do not commit unless 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 diagnose environment, tooling, and Agent Powerups setup problems.
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.