cli-forge-validate

To validate a Rust CLI project, run a 47-check compliance suite that verifies structural integrity, metadata, and runtime conventions. This process inspects your Cargo.toml and SKILL.md contract to produce a structured validation report.

A cli-forge compliance report is a machine-readable validation-report.yml file detailing pass/fail status, warnings, and remediation guidance. It works by enforcing a 47-check suite across categories like STRUCT, NAME, DEPS, META, SKILL, BUILD, TREE, HELP, DIR, CTX, ERR, REPL, and DAEMON.

Yes, CLI skill validation requires a valid Cargo.toml-based Rust project, the presence of .cli-forge/cli-plan.yml when in scope, and a SKILL.md contract. These files are necessary to verify structure, metadata, and daemon surfaces.

Check a scaffolded or takeover-adopted Rust CLI skill by applying the 47-check compliance suite across the design, plan, scaffold, and validate stages. This aligns the target project with the planning brief and contract surfaces to generate a structured compliance report.

This validation suite applies to scaffolded, takeover-adopted, and extended Rust CLI skills. It guides all three project types by enforcing the 47-check rules to ensure conformity with runtime conventions before publication.

Rust CLI skill validation fails when the project violates one or more of the 47 structural, metadata, or daemon surface checks. The generated validation-report.yml provides specific pass/fail status, warnings, and remediation guidance to fix the compliance issues.