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::schemafor the cited source of each rule. - invocation
- Invocation checks — actually run the documented CLI and catch drift between
what
SKILL.mdadvertises and what--helpactually offers. - result
- The result of a single
verifycheck. - schema
- The Claude Code schema constants that
verifyenforces.
Structs§
- Verify
Input - Where the invocation stage should look for skill text. Passed in so the
dispatcher owns the single
find_skill_filecall.
Enums§
- Output
Format - How
verifypresents its results (Improvement B). The human format is the default;jsonis for CI gating / scripting and uses the machine-readablecheck_ids already on eachCheckResult.
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.