bug-check
Run automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
Generate a dense state-restoration document before ending a session.
> /plugin marketplace add yeaight7/agent-powerupsHow it fires
How this command gets triggered: by you, by Claude, or both.
/write-handoffContext preview
What this command does when you run it.
Generate a dense state-restoration document before ending a session.
description: "Generate a dense state-restoration document before ending a session." argument-hint: "<current_status_summary>"
1. **Be Exact**: Vague summaries destroy context. Use exact file paths, line numbers, and error messages.
1. Parse the provided `$ARGUMENTS` summarizing the current state. 2. Identify the last modified files and the current failing test or goal. 3. Format the data into a strict Markdown structure: Goal, Current State (Working/Broken), Next Steps. 4. Overwrite or create `handoff.md` in the project root with this exact information. 5. Provide the exact command the next user should run to resume.
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.