Menu
Verify or record reviewed commit provenance, policy gates, and audit exports with fledge attest.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Validate, route, inspect, or run agent.3md manifests and typed tool templates.
Coordinate CorvidLabs agents through discovery, observation, execution, and verification.
Inspect spec ownership, drift, coverage, review queues, and gaps with fledge atlas.
Assess working-tree, staged, range, or CI change risk and gates with fledge augur.
Keep CI, pre-push verification, and release evidence tied to the current committed revision.
Build, modify, test, review, or release CorvidLabs Swift packages with Fledge-first and Swift 6 discipline.
| name | attest |
| description | Verify or record reviewed commit provenance, policy gates, and audit exports with fledge attest. |
Attest records review evidence for exact commits in Git notes (refs/notes/attest). Signing
is optional—an unsigned attestation is still a valid local record.
Use the Fledge plugin repo CorvidLabs/fledge-plugin-attest (not the standalone attest
kit alone). The public Fledge plugin targets macOS 13+.
fledge plugins install CorvidLabs/fledge-plugin-attest
fledge attest --help
fledge attest help sign
fledge attest help verify
fledge attest log -C . --json
fledge attest verify -C . --commit <sha> --json
fledge attest verify -C . --range <base>..<head> --json
Policy loads from .attest.json in the current working directory when present. Override
with --policy <path> only when using a non-default file (the path must exist). Treat a
missing or failed attestation as evidence to investigate, not permission to fabricate one.
Sign or record the exact reviewed SHA only after the verdict, confidence, tests, and reviewer identity are known:
fledge attest sign -C . --commit <sha> --reviewer <identity> --confidence <0-to-1> \
--verdict <proceed-or-review-or-block> --note <summary> --json
# Optional cryptographic signature (requires a signing key; generate with
# `fledge attest keygen` when that subcommand is present on the installed plugin)
fledge attest sign -C . --commit <sha> --reviewer <identity> --confidence <0-to-1> \
--verdict proceed --sign --json
# Optional: fold in prior Augur JSON (file path or `-` for stdin)
fledge attest sign -C . --commit <sha> --reviewer <identity> --from-augur <file-or--> --json
Add --tests-passed or --human-approved only when each statement is true. Publishing
refs/notes/attest is a separate remote write from creating the local note.
export always emits JSON (no --json flag):
fledge attest export -C .
fledge attest export -C . --range <base>..<head> --policy .attest.json
Preserve the commit SHA with every result.