bug-check
Run automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
Use to inspect a web UI with browser evidence before marking work complete.
> /plugin marketplace add yeaight7/agent-powerupsHow it fires
How this command gets triggered: by you, by Claude, or both.
/visual-reviewContext preview
What this command does when you run it.
Use to inspect a web UI with browser evidence before marking work complete.
Use to inspect a web UI with browser evidence before marking work complete.
Steps:
1. Confirm the dev server is running and Playwright MCP or equivalent is available. 2. Navigate to the target URL. Take a baseline screenshot and accessibility snapshot. 3. Check console errors on load. Flag any uncaught errors before continuing. 4. Exercise the target interaction with semantic selectors (role → text → label → testId → CSS). 5. Capture a screenshot after each significant state change. 6. Check network: did the expected API call fire and return a success status? 7. Check accessibility: are new elements keyboard-reachable and correctly labelled? 8. Report per scenario: expected, observed, evidence, PASS/FAIL/NEEDS_REVIEW.
Do not automate against production environments without explicit user approval.
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
Repo: yeaight7/agent-powerups
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.