Pular para o conteúdo
Novo

DeepSeek V4.1 Flash grátis por 7 dias: 10M tokens por dia após recarga de $10 ou mais. Até 30/11.

Como funciona
aeondave/verification-before-completionRelatórios e compliance

verification-before-completion

⁨Check evidence before reporting work complete, fixed, passing, or ready. Use at a completion boundary or when later changes may have invalidated an earlier result.⁩

v2026.11.13-21cd5683 instalações+3 em 7 dias39 EstrelasMITsincronizado há 10 horas

Instalar

Ainda não tem a CLI da NotHoly? Instale primeiro.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install aeondave/verification-before-completion

Grava em ⁦~/.notholy/skills⁩ depois de conferir a assinatura e o SHA-256.

AssinaturaAssinado, ed25519
Mb91943Npb…lU5v3TBA==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacote47e74fe7…9b1851aa
47e74fe7810d…39ce9b1851aa2 arquivos · ⁦2.5 KB⁩
VarreduraBaixo1 achado
  • Links para domínios externos
Ver a varredura completa
Fontegithub.com/AeonDave/malskill/tree/main/behaviours/verification-before-completion@21cd568

Este item ainda não foi escrito no seu idioma, então aparece em English.

Match each completion claim to evidence for the state being delivered. evidence-before-claims owns general evidence quality and uncertainty; this skill checks freshness and coverage.

Completion gate

  1. Name the outcome being claimed and the check that can detect its failure.
  2. Run the relevant check after the last change that could affect its result. Preserve required repository gates.
  3. Inspect exit status, substantive output, skipped cases, and the artifact or state actually checked.
  4. Map the evidence to acceptance criteria. Report uncovered requirements and unavailable checks explicitly.
  5. Investigate failures, correct in-scope causes, and rerun affected checks. Report unresolved failures and uncertain attribution. Once checks pass, repeat or broaden them only for a new change, failure, or unresolved concern.

A recorded result may be reused when its command, relevant inputs and checked state, environment, and coverage still apply. Compare changes since that result: a new turn, reader, commit, or unrelated edit does not alone invalidate it. Rerun affected checks when relevant inputs change; reverify when provenance or applicability cannot be established.

Select the check

Claim Useful evidence Limit
Tests pass Relevant suite on the delivered code Passing tests do not establish untested requirements.
Build succeeds Successful build for the intended target Lint alone does not establish a build.
Bug fixed Original failure reproduced and then resolved A nearby edit is not proof; disclose unavailable baseline reproduction.
Skill structure valid Frontmatter validation and resource sweep Structural checks do not prove behavior or token savings.
Delegated work complete Inspect diff/artifacts and corresponding check output Rerun when state, coverage, or provenance is insufficient; a summary alone is not evidence.
Remediation complete Relevant post-action state A successful command may not establish the intended effect.

Use diff inspection and required structural checks for low-impact editorial work; do not invent runtime tests that merely mirror text. Distinguish checks not run from checks that failed.

Load references/completion-evidence.md when choosing regression evidence, comparing implementation with an agreed design, or diagnosing an overstated completion claim.

Arquivos desta versão

Permissões

PermissãoDeclaradaEncontrada na varredura
Lê arquivosNãoNão
Grava arquivosNãoNão
Roda comandos no shellNãoNão
Usa a redeSimSim
Usa conectoresNãoNão
Controla um navegadorNãoNão

Achados da varredura

Revisado em 13 de nov. de 2026

  1. InfoLink · Links para domínios externos

Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.

VersãoPublicada emCommitSHA-256AssinaturaMudança de permissão
v2026.11.13-21cd56813 de nov. de 202621cd56847e74fe7Assinada–

Pergunte tudo o que o seu escopo permite.

Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.

  1. 1/3

    Crie a conta

    Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.

    Pessoa físicaEmpresa
  2. 2/3

    Adicione créditos

    No cartão. Você paga por token, sem assinatura.

    $5.00recarga mínima
  3. 3/3

    Pergunte

    No chat, ou instale o CLI e rode notholy login no terminal.

    $ notholy login