Cmd Done Check
Ask the agent whether it finished everything or has more to do — a lightweight completeness gate for the end of any task
Install
/plugin marketplace add Olshansk/agent-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add Olshansk/agent-skills --skill cmd-done-checkgit clone --depth 1 https://github.com/Olshansk/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/cmd-done-check ~/.claude/skills/cmd-done-checkPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Done Check A quick self-interrogation to catch loose ends before declaring a task complete. ## Instructions Answer each question honestly. If anything is incomplete, say so and ask the user whether to continue. ### 1. Did you do everything the user asked? - Re-read the original request. Is every explicit ask addressed? - Did you skip or defer anything without telling the user? - Did you say "I'll also..." or "next, we should..." and then not do it? ### 2. Did you leave any loose ends? - Are there TODOs, FIXMEs, or placeholder values you introduced that should be resolved now? - Are there commented-out blocks, debug prints, or temporary stubs in the output? - Are there follow-up steps you mentioned but didn't take? ### 3. Did you handle side effects? - Are there related files, configs, or tests that should be updated but weren't? - Did any rename, move, or deletion leave dangling references? - If you added a skill/command/export — is it wired up and discoverable? ### 4. Are docs and metadata consistent? - If you added or changed something user-facing, is the README or AGENTS.md updated? - Are variable names, comments, and doc strings consistent with what shipped? ## Output **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.
Details
- Skill name
cmd-done-check- Repository
- Olshansk/agent-skills
- Path
skills/cmd-done-check/SKILL.md- License
- MIT
- Repo updated
- 18 November 2026
FAQ
What does the Cmd Done Check skill do?
Ask the agent whether it finished everything or has more to do — a lightweight completeness gate for the end of any task
How do I install the Cmd Done Check skill?
Claude Code plugin: /plugin marketplace add Olshansk/agent-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Cmd Done Check popular?
It lives in Olshansk/agent-skills, which has 9 GitHub stars and 0 forks.
Related skills
Cmd Agent Persona Set
9Olshansk/agent-skills
Prime the agent with a behavioral persona for the conversation
Cmd Clean Code
9Olshansk/agent-skills
Improve code readability without altering functionality using idiomatic best practices
Cmd Code What
9Olshansk/agent-skills
Catch the user up on what the agent has been doing in the current session with 3-5 ultra-tight bullet points. Use when the user invokes /cmd-what, asks "what are you doing", "what did you do", "catch me up", "status", "where are we", or otherwise needs a fast situational summary of in-flight agent work.
Cmd Email Md
9Olshansk/agent-skills
Convert markdown to email-safe HTML with inline styles and cross-client compatibility. Use when writing newsletters, transactional emails, or any HTML email from markdown source.
Wp Social Email
9morrealev/wordpress-manager
This skill should be used when the user asks to "publish to social media", "schedule social posts", "send email campaign", "Mailchimp integration", "Buffer scheduling", "SendGrid email", "content distribution", "newsletter campaign", "email marketing", "social media management", "distribute content", or mentions publishing WordPress content to social and email channels.
Do
9borkweb/skills
Run a coding task through the matching pipeline (land an existing change, ship a new goal, or build a plan through complete) with concurrent steps, lean handoffs and council-answered design questions. Use for /do, "fix until safe to land", "keep working until ready" or "build, plan and implement this".
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.