返回 Skill 列表
extension
分类: 开发与工程无需 API Key

completion-integrity

防止在完成任务时走捷径和作弊。阻止带有警告抑制、被注释的测试或删除断言的提交。

person作者: jakexiaohubgithub

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:

  1. Explain WHY the suppression is necessary in the commit message
  2. The explanation should convince a reviewer
  3. If you can't explain it, fix the underlying issue instead

FAILURE CONDITIONS

You have FAILED if you:

  1. Commit code with integrity violations
  2. Claim "done!" without running actual verification
  3. Suppress warnings instead of fixing them
  4. Delete or comment out tests instead of fixing them
  5. Rationalize why these rules don't apply to you