// Ask the agent whether it finished everything or has more to do — a lightweight completeness gate for the end of any task
Audit personal skills for redundancy, verbosity, weak triggers, and overlap. Runs a Claude→Codex review loop, presents per-item approval checkboxes, then applies approved edits and updates README and agent metadata. Use when asked to "review my skills", "audit my skills", "revisit my skills", or "clean up my skills". Accepts an optional skill name to scope the review to a single skill.
Set up or extend golden/snapshot tests for a project. Covers fixture design, Makefile targets, snapshot storage, diff workflow, and update protocol.
Resolve merge conflicts systematically with context-aware 3-tier classification and escalation protocol
Reshape code for readability, naming, structure, TODOs, and reduced surface area across any language
Create or improve Makefiles with minimal complexity. Templates available: base, python-uv, python-fastapi, postgres, nodejs, go, chrome-extension, flutter, electron, static-site.
Build high-signal PR context for review with diff analysis, risk assessment, and discussion questions
| name | cmd-done-check |
| description | Ask the agent whether it finished everything or has more to do — a lightweight completeness gate for the end of any task |
| disable-model-invocation | false |
A quick self-interrogation to catch loose ends before declaring a task complete.
Answer each question honestly. If anything is incomplete, say so and ask the user whether to continue.
If everything is done: say "Done — nothing left." in one line.
If something is incomplete: list each item as a bullet with what's missing and why, then ask:
Want me to continue and handle these now, or are you good?
Do not pad the response. One sentence per finding.