check-completion
Check Completion
Two-phase audit-and-remediate skill. Phase 1 — Audit: scan task / session / plan / branch claims, classify every item into one of 22 statuses with cited evidence, deliver a markdown table. Phase 2 — Remediate: drive every in-scope row to a terminal status — Implemented for finished work, or a deliberate-stop terminal (Deferred to Human, Deprioritized, Cancelled, Out of Scope, Superseded with replacement verified, or Blocked — unresolvable with concrete next step). No mid-task pauses. No defaulting to Implemented on faith.
When to use
- "are we done?" / "what's left?" / "did we actually finish X?"
- verifying a claimed-done session, plan, branch, or PR before declaring complete
- producing a status report on a multi-step task with evidence per item
- catching silent gaps — tasks that were started, assumed complete, deferred, or forgotten
- recovering from a crashed / interrupted / half-finished execution by enumerating what remains
- converting a casual "I think we're good" into a rigorous completion audit
- triaging a TodoList where statuses drifted from reality
Do NOT use when:
- verifying a single claim before making it — use the Gate Function inline as a local verification gate, not the full audit
- evaluating reviewer comments, bot comments, or external review docs →
evaluate-code-review - planning upcoming work from GitHub issues →
run-issue-tree
More from yigitkonur/skills-by-yigitkonur
run-research
Use skill if you are answering one technical research question with current web evidence, Reddit practitioner experience, and source-backed synthesis, optionally fanned out across parallel subagents.
42run-agent-browser
Use skill if you are driving the agent-browser CLI for ad hoc browser automation — @ref snapshots, sessions, forms, extraction, screenshots, headed/stealth, or provider runs.
38publish-npm-package
Use skill if you are publishing to npm via GitHub Actions release workflow with trusted publishing, NPM_TOKEN, provenance, semantic-release, changesets, release-please, or fixing npm publish CI.
35init-agent-config
Use skill if you are creating, auditing, or migrating CLAUDE.md, AGENTS.md, or REVIEW.md instruction files, folder-scoped agent guidance, or cross-agent companion entrypoints.
34build-mcp-use-server
Use skill if you are building TypeScript MCP servers with mcp-use/server — server.tool, response helpers, ctx.auth, sessions, transports, widgets, Inspector, deploy.
34build-skills
Use skill if you are creating or substantially revising a Claude skill and need workspace-first evidence, remote comparison, and repo-fit synthesis before writing SKILL.md.
32