Skip to main content

Module verify

Module verify 

Source
Expand description

The skillpack verify subcommand: load the generated distribution files and run discovery + invocation checks against them.

Design §5.2. verify works even on hand-written plugin files (not just init output) — see §4.2 — so the loader is tolerant of missing pieces and each check degrades gracefully.

Re-exports§

pub use self::result::VerifyReport;

Modules§

discovery
Discovery checks — structural validation against the documented Claude Code plugin schema. Pure functions; the only I/O is the file reads the caller hands us. See crate::verify::schema for the cited source of each rule.
invocation
Invocation checks — actually run the documented CLI and catch drift between what SKILL.md advertises and what --help actually offers.
result
The result of a single verify check.
schema
The Claude Code schema constants that verify enforces.

Structs§

VerifyInput
Where the invocation stage should look for skill text. Passed in so the dispatcher owns the single find_skill_file call.

Enums§

OutputFormat
How verify presents its results (Improvement B). The human format is the default; json is for CI gating / scripting and uses the machine-readable check_ids already on each CheckResult.

Functions§

render
Pretty-print a report as the human-facing output (design §5.2 step 4). Returns a single string the CLI writes to stdout.
render_json
Render the report as a stable JSON object for CI / scripting. Shape: { "ok": bool, "counts": {pass,warn,fail,skip}, "results": [ {check_id, check_name, severity, message, suggestion?, location?} ... ] }.
run
Run the full verify suite against root, returning the aggregate report.