feat(marketplace): command consolidation + 8 new plugins (v8.1.0 → v9.0.0) [BREAKING]

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>
This commit is contained in:
2026-02-06 14:52:11 -05:00
parent 5098422858
commit 2d51df7a42
321 changed files with 13582 additions and 1019 deletions

View File

@@ -0,0 +1,27 @@
# Deploy Pipeline Integration
Add to your project's CLAUDE.md:
## Deployment Management (ops-deploy-pipeline)
This project uses the **ops-deploy-pipeline** plugin for Docker Compose deployment configuration, validation, and rollback planning.
### Available Commands
| Command | Description |
|---------|-------------|
| `/deploy setup` | Setup deployment configuration for this project |
| `/deploy generate` | Generate docker-compose.yml, Caddyfile, systemd units |
| `/deploy validate` | Validate configs for correctness and best practices |
| `/deploy env` | Manage .env.development / .env.production files |
| `/deploy check` | Pre-deployment health check (system resources, ports, Docker) |
| `/deploy rollback` | Generate rollback plan with volume backup steps |
### Usage Guidelines
- Run `/deploy setup` first to establish project deployment profile
- Use `/deploy generate` to create initial configs, then customize
- Always run `/deploy validate` before deploying to catch issues
- Use `/deploy check` on the target server before `docker compose up`
- Generate a `/deploy rollback` plan before any production deployment
- Never commit `.env.production` or `.env.staging` to version control