bug-check
CommandRun automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
Audit the repository's documentation for broken paths, missing setup commands, and stale code blocks.
> /plugin marketplace add yeaight7/agent-powerups
description: "Audit the repository's documentation for broken paths, missing setup commands, and stale code blocks." argument-hint: "<directory_to_audit>"
1. **Focus on Accuracy, Not Style**: Do not critique grammar. Critique technical accuracy and executability.
1. Find all `.md` files in the target directory. 2. Extract all shell commands. Check if they are standard and complete (e.g., not missing arguments). 3. Extract all file paths referenced in the text. Run a quick check to see if those files exist in the repo. 4. Generate an Audit Report detailing stale paths, non-executable commands, and missing architecture pointers.
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.