How this command is triggered — by the user, by Claude, or both
Slash command
/specs:validateThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# Validate Specifications Validate YAML spec files in `docs.specs/` against their JSON schemas. ## Step 0: Get Plugin Path Read `~/.claude/plugins/cache/settings.json` and get the `pluginPath` from the `cc-specs-plugin` entry. ## Step 1: Check Dependencies Check if `node_modules` exists in the plugin's `validator/` directory. If not, run: ## Step 2: Run Validation Script Run the Node.js validation script: The script outputs JSON with validation results in this format: ## Step 3: Report Results Parse the JSON output and report results in a user-friendly format: ### If all sp...
Validate YAML spec files in docs.specs/ against their JSON schemas.
Read ~/.claude/plugins/cache/settings.json and get the pluginPath from the cc-specs-plugin entry.
Check if node_modules exists in the plugin's validator/ directory. If not, run:
npm install --prefix "<pluginPath>/validator"
Run the Node.js validation script:
node "<pluginPath>/validator/validate.js" --specs "docs.specs" --schemas "<pluginPath>/schemas"
The script outputs JSON with validation results in this format:
{
"summary": { "total": 10, "valid": 8, "invalid": 2 },
"results": [
{ "file": "domain/event/event.yaml", "schema": "entity", "valid": true },
{ "file": "system.yaml", "schema": "system", "valid": false,
"errors": [{ "path": "/users/0", "message": "must have required property 'name'" }] }
]
}
Parse the JSON output and report results in a user-friendly format:
Report the total count and list each file with a checkmark.
For each invalid spec:
Group errors by file for readability.
End with a summary line: "X of Y specs passed validation"
npx claudepluginhub codingawayy/cc-marketplace --plugin specs/validate-specValidates OpenAPI spec (YAML/JSON) for structural correctness, references, completeness, and best practices. Reports issues by severity with fix suggestions and summarizes version, endpoints, schemas.
/validateValidates a completed implementation against the provided spec file by comparing code, git changes, and conventions, surfacing all gaps and discrepancies.
/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.