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.5 KiB
1.5 KiB
name, description
| name | description |
|---|---|
| cv status | Marketplace-wide health check across all installed plugins |
/cv status
Purpose
Quick health check showing installed plugin status. For each marketplace plugin, reports installation state, MCP connectivity, and configuration status.
Usage
/cv status # Full status table
/cv status --plugin projman # Single plugin check
Workflow
Step 1: Enumerate Plugins
Read .claude-plugin/marketplace.json to get the full plugin list.
Step 2: Check Each Plugin
For each plugin, verify:
- Installed:
plugin.jsonexists and is valid JSON - MCP Connected: If plugin has MCP servers (check
metadata.json), verify server is responding - Configured: Required config files present
- Version: Read from
plugin.json - Domain: Read from
plugin.json
Step 3: Display Results
| Plugin | Domain | Version | Installed | MCP | Configured |
|--------------------------|--------|---------|-----------|-----|------------|
| projman | core | 3.4.0 | Y | Y | Y |
| git-flow | core | 1.2.0 | Y | - | Y |
| cmdb-assistant | ops | 1.2.0 | Y | N | N |
Summary: 12/12 installed, 4/5 MCP connected, 11/12 configured
Notes
- MCP column shows
-for plugins without MCP servers Nin MCP means the server is defined but not respondingNin Configured means the setup check found issues