completion-integrity
Prevents shortcuts and cheating when completing tasks. Blocks commits with warning suppressions, commented tests, or deleted assertions.
When & Why to Use This Skill
The Completion Integrity skill is a specialized Git pre-commit hook designed to enforce high-standard development practices and maintain codebase health. It acts as a critical guardrail for both human developers and AI agents by automatically detecting and blocking 'shortcuts' such as suppressed warnings, commented-out tests, or deleted assertions. By ensuring that tasks are completed with genuine fixes rather than bypasses, it significantly improves long-term code reliability and prevents the accumulation of technical debt.
Use Cases
- AI Agent Supervision: Prevent AI coding assistants from 'cheating' by commenting out failing tests or deleting assertions to falsely claim a task is complete.
- Continuous Integration Quality Gate: Use as a local pre-commit check to ensure that no code with suppressed ESLint/Pragma warnings or empty catch blocks enters the repository.
- Test Suite Integrity: Protect the robustness of the testing environment by blocking commits that attempt to delete test files or reduce the number of active assertions to bypass CI/CD failures.
- Technical Debt Control: Maintain code standards by limiting the number of new 'TODO' comments and preventing the silencing of critical compiler or linter warnings.
| name | completion-integrity |
|---|---|
| description | Prevents 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