bug-check
CommandRun automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
Review the README.md to ensure it functions as an executable contract for new developers.
> /plugin marketplace add yeaight7/agent-powerups
description: "Review the README.md to ensure it functions as an executable contract for new developers." argument-hint: "<path/to/readme>"
1. **Assume Zero Context**: Review the file assuming the reader knows nothing about the stack or the project history.
1. Read the target README file. 2. Check for a clear statement of purpose. 3. Check for a `.env` or configuration setup section. 4. Check for an exact, copy-pasteable build/install command. 5. Check for an exact, copy-pasteable test command. 6. If any are missing or ambiguous, output a diff to fix the README immediately.
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.