lmiranda
271e0210a5
All 25 dispatch files now have name: in frontmatter with Workflow section that displays sub-commands and prompts for selection. Bare /noun invocation is now useful instead of a dead end. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
28 lines
899 B
Markdown
28 lines
899 B
Markdown
---
|
|
name: gitflow
|
|
description: Git workflow automation with safety enforcement — type /gitflow <action> for commands
|
|
---
|
|
|
|
# /gitflow
|
|
|
|
Git workflow automation with smart commits, branch management, and safety enforcement.
|
|
|
|
When invoked without a sub-command, display available actions and ask which to run.
|
|
|
|
## Available Commands
|
|
|
|
| Command | Description |
|
|
|---------|-------------|
|
|
| `/gitflow setup` | Configure git-flow for the current project |
|
|
| `/gitflow commit` | Smart commit with optional --push, --merge, --sync |
|
|
| `/gitflow branch-start` | Create a properly-named feature branch |
|
|
| `/gitflow branch-cleanup` | Clean up merged/stale branches |
|
|
| `/gitflow status` | Enhanced git status with recommendations |
|
|
| `/gitflow config` | Configure git-flow settings |
|
|
|
|
## Workflow
|
|
|
|
1. Display the table above
|
|
2. Ask: "Which command would you like to run?"
|
|
3. Route to the selected sub-command
|