Fähigkeiten completion-integrity
📦

completion-integrity

Niedriges Risiko ⚙️ Externe Befehle

Enforce code completion integrity

Developers often take shortcuts when completing tasks. This skill provides a git pre-commit hook that blocks commits with integrity violations like warning suppressions, commented tests, and deleted assertions.

UnterstĂĽtzt: Claude Codex Code(CC)
đź“Š 69 Angemessen
1

Die Skill-ZIP herunterladen

2

In Claude hochladen

Gehe zu Einstellungen → Fähigkeiten → Skills → Skill hochladen

3

Einschalten und loslegen

Teste es

Verwendung von "completion-integrity". A developer attempts to commit code with eslint-disable-next-line comments suppressing lint warnings

Erwartetes Ergebnis:

Commit BLOCKED by completion-integrity hook. Reason: Warning suppression detected (eslint-disable). The hook requires developers to fix the underlying issue or document why suppression is necessary in the commit message.

Verwendung von "completion-integrity". A developer deletes 3 assertions from a test file to make tests pass

Erwartetes Ergebnis:

Commit BLOCKED by completion-integrity hook. Reason: Deleted assertions detected (3 total). Removing test checks does not fix bugs. The developer must restore the assertions or fix the underlying code issues.

Verwendung von "completion-integrity". A developer commits code with 5 new TODO comments

Erwartetes Ergebnis:

Commit BLOCKED by completion-integrity hook. Reason: Fresh TODOs detected (5, limit is 2). The developer should defer work by creating explicit tickets rather than leaving undocumented TODOs.

Sicherheitsaudit

Niedriges Risiko
v6 • 1/21/2026

All 14 static findings are false positives. Network finding is standard GitHub URL metadata. Weak cryptographic algorithm flags are triggered by benign words like 'integrity'. Shell command detections are legitimate bash invocations for git hook scripts, not backtick execution. This is a benign development quality tool.

2
Gescannte Dateien
272
Analysierte Zeilen
1
befunde
6
Gesamtzahl Audits

Risikofaktoren

⚙️ Externe Befehle (3)
SKILL.md:12-14 SKILL.md:20 SKILL.md:29-31
Auditiert von: claude Audit-Verlauf anzeigen →

Qualitätsbewertung

38
Architektur
100
Wartbarkeit
87
Inhalt
31
Community
90
Sicherheit
91
Spezifikationskonformität

Was du bauen kannst

Prevent testing shortcuts

Team leads can ensure developers do not delete or comment out tests to make code appear to work. The hook blocks commits with test integrity violations.

Maintain code quality standards

Enforce that developers fix warnings rather than suppressing them. The hook catches eslint-disable and pragma warning disable patterns.

Document deferred work properly

Force developers to create explicit tickets for deferred work rather than leaving undocumented TODOs. The hook limits fresh TODOs per commit.

Probiere diese Prompts

Install the integrity hook 
Install the completion-integrity git pre-commit hook by running: bash "${CLAUDE_PLUGIN_ROOT}/scripts/install-git-hook.sh"
Check for integrity violations 
Run a manual integrity check on the current state of the repository using: bash "${CLAUDE_PLUGIN_ROOT}/scripts/integrity-check.sh"
Review blocked commit 
My commit was blocked by the integrity hook. The violation was: [describe violation]. Explain why this is flagged and how to fix it properly.
Understand false positive handling 
I need to commit code with a legitimate warning suppression. How do I handle this with the completion-integrity hook while providing proper documentation?

Bewährte Verfahren

  • Fix the underlying issue rather than suppressing warnings or deleting tests
  • Document legitimate suppressions in commit messages with clear justification
  • Create tickets for deferred work instead of leaving undocumented TODOs
  • Run manual integrity checks before committing to catch issues early

Vermeiden

  • Using eslint-disable or pragma warning disable to hide lint errors
  • Commenting out or deleting tests to make them pass
  • Removing test assertions instead of fixing failing code
  • Leaving TODO comments without creating tracking tickets

Häufig gestellte Fragen

What happens when the hook blocks my commit?
The hook displays the specific integrity violation detected. You must address the issue or provide justification in your commit message before the commit will be accepted.
Can I bypass the hook for legitimate cases?
You can still commit by explaining why the suppression or pattern is necessary in your commit message. The explanation should convince a reviewer that the exception is justified.
What patterns does the hook detect?
The hook detects warning suppressions, commented-out tests, deleted assertions, test file deletion, empty catch blocks, and excessive fresh TODOs in a single commit.
Does this work with all git workflows?
The hook integrates with standard git pre-commit workflows. It requires the CLAUDE_PLUGIN_ROOT environment variable to locate the installation scripts.
Can I customize the thresholds?
The current version enforces fixed thresholds (2 fresh TODOs, 2+ deleted assertions). Customization would require modifying the underlying integrity-check.sh script.
Is this suitable for all team sizes?
The hook is valuable for teams of any size that want to enforce code quality standards. Smaller teams may want to adjust thresholds to match their workflow.

Entwicklerdetails

Autor

ANcpLua

Lizenz

MIT

Repository

https://github.com/ANcpLua/ancplua-claude-plugins/tree/main/plugins/completion-integrity/skills/completion-integrity

Ref

main

Dateistruktur

đź“„ SKILL.md