olshansk/cmd-done-check
skills/cmd-done-check/SKILL.md
Ask the agent whether it finished everything or has more to do — a lightweight completeness gate for the end of any task
$ install --global
skillsauthnpx skillsauth add olshansk/agent-skills cmd-done-checkInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 21, 2026, 6:37 AM140.9s1 file scanned
SKILL.md
- 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
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.
Related Skills
olshansk/cmd-skills-review
development
VerifiedTrustedCommunity
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.
7SKILL.mdUpdated May 17, 2026
olshansk/cmd-golden-tests
development
VerifiedTrustedCommunity
Set up or extend golden/snapshot tests for a project. Covers fixture design, Makefile targets, snapshot storage, diff workflow, and update protocol.
7SKILL.mdUpdated May 9, 2026
olshansk/cmd-write-proofread
development
VerifiedTrustedCommunity
Proofread posts before publishing for spelling, grammar, repetition, logic, weak arguments, broken links, and optionally reformat for skimmability or shape the writing vibe toward a known author's style
7SKILL.mdUpdated May 4, 2026
olshansk/cmd-skills-local-repo
tools
VerifiedTrustedCommunity
Scaffold cross-tool repo-local skills and agent instructions with canonical source in .agents/ and symlinks for Claude, Codex, Gemini, and Codex-home
7SKILL.mdUpdated May 4, 2026