Vai al contenuto
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
aeondave/verification-before-completionReport 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 installazioni+3 in 7 giorni39 StelleMITsincronizzato 10 ore fa

Installa

Non hai ancora la CLI di NotHoly? Installala prima.

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

Scrive in ⁦~/.notholy/skills⁩ dopo aver controllato la firma e lo SHA-256.

FirmaFirmato, ed25519
Mb91943Npb…lU5v3TBA==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchetto47e74fe7…9b1851aa
47e74fe7810d…39ce9b1851aa2 file · ⁦2.5 KB⁩
ScansioneBasso1 segnalazione
  • Link a domini esterni
Vedi la scansione completa
Sorgentegithub.com/AeonDave/malskill/tree/main/behaviours/verification-before-completion@21cd568

Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: 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.

File di questa versione

Permessi

PermessoDichiaratoTrovato dalla scansione
Legge fileNoNo
Scrive fileNoNo
Esegue comandi shellNoNo
Usa la reteSìSì
Usa i connettoriNoNo
Controlla un browserNoNo

Segnalazioni della scansione

Rivisto il 13 nov 2026

  1. InfoLink · Link a domini esterni

Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.

VersionePubblicataCommitSHA-256FirmaCambio di permessi
v2026.11.13-21cd56813 nov 202621cd56847e74fe7Firmata–

Chiedi tutto quello che il tuo perimetro consente.

Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.

  1. 1/3

    Crea l'account

    Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.

    PrivatoAzienda
  2. 2/3

    Aggiungi crediti

    Con carta. Paghi a token, senza abbonamento.

    $5.00ricarica minima
  3. 3/3

    Chiedi

    In chat, oppure installa la CLI ed esegui notholy login nel terminale.

    $ notholy login