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.0 KiB
1.0 KiB
git-flow - CLAUDE.md Integration
Add the following section to your project's CLAUDE.md file to enable git-flow.
Git Workflow
This project uses the git-flow plugin for git operations.
Workflow Style
Style: feature-branch Base Branch: development
Branch Naming
Use the format: <type>/<description>
Types: feat, fix, chore, docs, refactor, test, perf
Examples:
feat/add-user-authfix/login-timeoutchore/update-deps
Commit Messages
Use conventional commits:
<type>(<scope>): <description>
[body]
[footer]
Commands
| Command | Use Case |
|---|---|
/gitflow commit |
Smart commit with optional --push, --merge, --sync |
/gitflow commit --push |
Commit and push to remote |
/gitflow commit --merge |
Commit and merge into target branch |
/gitflow branch-start |
Start new branch |
/gitflow status |
Enhanced status |
Protected Branches
Do not commit directly to: main, development, staging
Copy the section between the horizontal rules into your CLAUDE.md.