contact715

Completion Audit — Security skill for Claude Code

Security community

Skill: Completion audit — mandatory before any "done" claim.

How to install Completion Audit

Installs to ~/.claude/skills/contact715-jidoka-completion-audit/SKILL.md

Terminal
mkdir -p ~/.claude/skills/contact715-jidoka-completion-audit && curl -fsSL https://raw.githubusercontent.com/contact715/jidoka/HEAD/.claude/skills/completion-audit.md -o ~/.claude/skills/contact715-jidoka-completion-audit/SKILL.md

Restart Claude Code, or start a new session, for it to be picked up.

What Completion Audit does

Skill: Completion audit — mandatory before any "done" claim

Wave: wave-145 | Status: experimental | Tags: [meta, process, anti-tunnel-vision, closure, quality-gate]


When to use

This skill fires **before any message** where the AI is about to write "done", "shipped", "complete", or "closed". It is not optional. Skipping it is the `optimistic-completion-bias` anti-pattern (`docs/ANTI_PATTERNS_CATALOG.md` entry 3).

Use in every situation where:

  • A task, wave, or fix is being de

Alternatives in Security

  • Skill Coverage Audit — Trace codepaths in diffs, map against tests, auto-generate missing coverage — use before shipping PRs 2.8k ★
  • Release Audit — Use right before cutting a release — it spawns ONE fresh sibling session via CCC that audits only the JUDGMENT 130 ★
  • Mobile Resume — Audit an unfinished mobile app, create a completion plan, then implement remaining work after approval 107 ★

Full documentation available on GitHub

View Source Repository