completion-integrity
// Prevents shortcuts and cheating when completing tasks. Blocks commits with warning suppressions, commented tests, or deleted assertions.
$ git log --oneline --stat
stars:194
forks:37
updated:March 4, 2026
SKILL.mdreadonly
SKILL.md Frontmatter
namecompletion-integrity
descriptionPrevents shortcuts and cheating when completing tasks. Blocks commits with warning suppressions, commented tests, or deleted assertions.
Completion Integrity
Git pre-commit hook that blocks commits with integrity violations.
Install
bash "${CLAUDE_PLUGIN_ROOT}/scripts/install-git-hook.sh"
What It Catches
| Pattern | Why It's Bad |
|---|---|
Warning suppression (#pragma warning disable, eslint-disable) | Hides problems instead of fixing them |
| Commented-out tests | Tests exist for a reason |
| Deleted assertions (>2) | Removing checks doesn't fix bugs |
| Test file deletion | Don't delete tests to make them "pass" |
| Empty catch blocks | Swallowing errors hides failures |
| Fresh TODOs (>2 per commit) | Defer work explicitly, not via comments |
Manual Check
bash "${CLAUDE_PLUGIN_ROOT}/scripts/integrity-check.sh"
False Positives
Sometimes suppressions are legitimate. If blocked:
- Explain WHY the suppression is necessary in the commit message
- The explanation should convince a reviewer
- If you can't explain it, fix the underlying issue instead
FAILURE CONDITIONS
You have FAILED if you:
- Commit code with integrity violations
- Claim "done!" without running actual verification
- Suppress warnings instead of fixing them
- Delete or comment out tests instead of fixing them
- Rationalize why these rules don't apply to you