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>
2.1 KiB
2.1 KiB
Skill: MCP Tools Reference
Available MCP tools for contract-validator operations.
Tool Categories
Parse Tools
| Tool | Description |
|---|---|
parse_plugin_interface |
Extract interface from plugin README.md |
parse_claude_md_agents |
Extract agents and tool sequences from CLAUDE.md |
Validation Tools
| Tool | Description |
|---|---|
validate_compatibility |
Check two plugins for conflicts |
validate_agent_refs |
Check agent tool references exist |
validate_data_flow |
Verify data flow through agent sequence |
validate_workflow_integration |
Check domain plugin exposes required advisory interfaces and gate contract version |
Report Tools
| Tool | Description |
|---|---|
generate_compatibility_report |
Generate full marketplace report (JSON) |
list_issues |
Filter issues by severity or type |
Tool Usage Patterns
Full Marketplace Validation
1. generate_compatibility_report(marketplace_path)
2. list_issues(severity="ERROR") # Get critical issues
3. list_issues(severity="WARNING") # Get warnings
Single Agent Check
1. parse_claude_md_agents(claude_md_path)
2. validate_agent_refs(agent_name, agents_data)
3. validate_data_flow(agent_workflow)
Interface Listing
1. For each plugin:
parse_plugin_interface(readme_path)
2. Aggregate results into summary table
Dependency Graph
1. generate_compatibility_report(marketplace_path)
2. validate_data_flow(cross_plugin_flows)
3. Build Mermaid diagram from results
Workflow Integration Check
1. validate_workflow_integration(plugin_path, domain_label) # Check single domain plugin
2. validate_workflow_integration(plugin_path, domain_label, expected_contract="v1") # With contract version check
3. For each domain in domain-consultation.md detection rules:
validate_workflow_integration(domain_plugin_path, domain_label, expected_contract)
Error Handling
If MCP tools fail:
- Check if
/cv setuphas been run - Verify session was restarted after setup
- Check MCP server venv exists and is valid