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.2 KiB
1.2 KiB
name, description, agent
| name | description | agent |
|---|---|---|
| gitflow branch-start | Create a new feature/fix/chore branch with consistent naming | git-assistant |
/gitflow branch-start - Start New Branch
Skills
- skills/visual-header.md
- skills/branch-naming.md
- skills/git-safety.md
- skills/environment-variables.md
Purpose
Create a new branch with consistent naming conventions, based on the configured base branch.
Parameters
| Parameter | Description |
|---|---|
<description> |
Brief description for branch name |
--type |
Branch type: feat, fix, chore, docs, refactor |
--issue |
Issue number to include in branch name |
Workflow
- Display header - Show GIT-FLOW Branch Start header
- Determine type - Prompt for branch type if not provided
- Get description - Prompt for description if not provided
- Generate name - Convert to kebab-case (per branch-naming.md)
- Validate - Check naming rules, truncate if needed
- Update base - Checkout and pull base branch
- Create branch -
git checkout -b <new-branch> - Confirm - Display created branch info
Output
Branch: feat/add-user-authentication
Base: development @ abc1234
Status: Ready for development