How this command is triggered — by the user, by Claude, or both
Slash command
/jsf:validateThe summary Claude sees in its command listing — used to decide when to auto-load this command
Dispatch the validator agent for the current in-progress phase. The validator runs automated tests, reports results, and if manual validation is required per the `validation-gate` skill, prompts the user for explicit confirmation. Do not mark a phase complete until both criteria pass.
Dispatch the validator agent for the current in-progress phase. The validator runs automated tests, reports results, and if manual validation is required per the validation-gate skill, prompts the user for explicit confirmation. Do not mark a phase complete until both criteria pass.
npx claudepluginhub jmeagher/software-factory --plugin jsf/validateValidates CLI harness for software at given path or GitHub repo against HARNESS.md standards: directory structure, files, Click CLI, core modules, tests, and docs.
/validateValidates a bug bounty finding through a structured 7-question gate and 4-gate checklist, killing weak submissions before report writing.
/validateValidates an OpenAPI/Swagger spec using the kubb validate CLI. Reports errors with line-level suggestions and offers next steps like /kubb:generate.
/validateValidates project structure, git config, build setup, code quality, CI/CD workflows, and best practices; reports issues, score, and recommendations with --path and --verbose options.
/validateValidates OSCAL documents (JSON, XML, YAML) against NIST JSON schemas, checking conformance, required fields, enums, UUIDs, and version. Outputs status, errors, or JSON for CI.
/validateValidates cli-anything-web CLI at <app-path> against HARNESS.md standards across 11 categories (75 checks), reporting N/N pass/fail counts and fix suggestions for failures.