Receber por email
← Voltar para o catálogo

completion-integrity

Prevents shortcuts and cheating when completing tasks. Blocks commits with warning suppressions, commented tests, or deleted assertions.

367estrelas
Atualizado há 4 meses

Ver no GitHub ↗

Como adicionar

/plugin marketplace add aiskillstore/marketplace

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/completion-integrity/svg)](https://www.skillteca.com.br/skills/completion-integrity)

Skills relacionadas

Ver todas de Segurança →

Alerta por categoria

Receba novas skills de Segurança toda segunda

1 email curto, só com as skills novas de Segurança. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

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
Compartilhar X LinkedIn