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 check-agent |
/cv check-agent
Skills to Load
- skills/visual-output.md
- skills/interface-parsing.md
- skills/validation-rules.md
- skills/mcp-tools-reference.md
Usage
/cv check-agent <agent_name> [claude_md_path]
Parameters
agent_name(required): Agent to validate (e.g., "Planner", "Orchestrator")claude_md_path(optional): Path to CLAUDE.md. Defaults to./CLAUDE.md
Workflow
-
Display header per
skills/visual-output.md -
Parse agent per
skills/interface-parsing.md- Use
parse_claude_md_agentsto extract agent definition - Get responsibilities, tool references, workflow steps
- Use
-
Validate per
skills/validation-rules.md- Use
validate_agent_refs- check all tools exist - Use
validate_data_flow- verify producer/consumer order
- Use
-
Report findings:
- Tool references found
- Missing tools (with suggestions)
- Data flow issues
- Recommendations
Examples
/cv check-agent Planner
/cv check-agent Orchestrator ./CLAUDE.md
/cv check-agent data-analysis ~/project/CLAUDE.md