lmiranda
2d51df7a42
Phase 1b: Rename all ~94 commands across 12 plugins to /<noun> <action> sub-command pattern. Git-flow consolidated from 8→5 commands (commit variants absorbed into --push/--merge/--sync flags). Dispatch files, name: frontmatter, and cross-reference updates for all plugins. Phase 2: Design documents for 8 new plugins in docs/designs/. Phase 3: Scaffold 8 new plugins — saas-api-platform, saas-db-migrate, saas-react-platform, saas-test-pilot, data-seed, ops-release-manager, ops-deploy-pipeline, debug-mcp. Each with plugin.json, commands, agents, skills, README, and claude-md-integration. Marketplace grows from 12→20. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1.1 KiB
1.1 KiB
name
| name |
|---|
| cv validate |
/cv validate
Skills to Load
- skills/visual-output.md
- skills/plugin-discovery.md
- skills/interface-parsing.md
- skills/validation-rules.md
- skills/mcp-tools-reference.md
Usage
/cv validate [marketplace_path]
Parameters
marketplace_path(optional): Path to marketplace root. Defaults to current project root.
Workflow
-
Display header per
skills/visual-output.md -
Discover plugins per
skills/plugin-discovery.md -
Parse interfaces per
skills/interface-parsing.md- Use
parse_plugin_interfacefor each plugin
- Use
-
Run validations per
skills/validation-rules.md- Use
validate_compatibilityfor pairwise checks - Use
validate_agent_refsfor CLAUDE.md agents - Use
validate_data_flowfor data sequences - Use
validate_workflow_integrationfor domain plugin advisory interfaces
- Use
-
Generate report:
- Use
generate_compatibility_reportfor full report - Use
list_issuesto filter by severity - Display summary and actionable suggestions
- Use
Examples
/cv validate
/cv validate ~/claude-plugins-work