bug-check
CommandRun automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
Use when a change is ready to be tagged and published.
> /plugin marketplace add yeaight7/agent-powerups
Use when a change is ready to be tagged and published.
Steps:
1. Read the current version from `package.json` or the relevant manifest. 2. Confirm the compare range: `git log <last-tag>..HEAD --oneline --no-merges`. 3. Verify changelog coverage. Every user-visible commit must appear in the release notes. 4. Run `npm test`. All tests must pass before proceeding. 5. Run `tsc --noEmit` if the project has a TypeScript build step. 6. Scan for breaking changes: commits with `!` suffix or `BREAKING CHANGE:` in the body. 7. Write the exact publish plan: commands in sequence. 8. Write the rollback plan: one reversal per publish step. 9. Present the go/no-go readout and wait for explicit approval before executing.
Do not tag, publish, or push until the user explicitly approves the plan.
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.