bug-check
CommandRun automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
Record a brief Architecture Decision Record (ADR) about a recent technical choice.
> /plugin marketplace add yeaight7/agent-powerups
description: "Record a brief Architecture Decision Record (ADR) about a recent technical choice." argument-hint: "<decision_summary>"
1. **Keep it Terse**: An ADR is a factual record, not a blog post. Focus on the constraints and the decision. 2. **Don't Overcomplicate**: Do not generate massive templates. Stick to Context, Decision, and Consequences.
1. Parse the `$ARGUMENTS` to understand the decision made. 2. Determine if a `docs/adr/` directory exists. If not, create it. 3. Draft a short Markdown document named `YYYY-MM-DD-<slug>.md`. 4. Include the problem context, the chosen solution, and the accepted trade-offs. 5. Save the file and confirm its creation.
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.