Skills overview
Eleven skills. Each is invokable directly via /vibe-flow:<skill>, or used as a
sub-skill by a higher-level one.
| Skill | Invoke | Purpose |
|---|---|---|
| vibe-init | /vibe-flow:vibe-init | First-time setup: pick project, scaffold .vibe-flow.yaml + state.json |
| vibe-plan | /vibe-flow:vibe-plan <spec> | Decompose a spec into an atomic issue tree with deps + tiers |
| vibe-ship | /vibe-flow:vibe-ship | Wave-based parallel dispatch with executor routing |
| vibe-link | /vibe-flow:vibe-link | Link pushed branch to a GitHub PR; move issue to in_review |
| vibe-review | /vibe-flow:vibe-review <PR> | Two-stage review by a fresh subagent; post to PR |
| vibe-merge | /vibe-flow:vibe-merge <PR> | Verify gates, squash merge, close loop |
| vibe-dispatch-fix | /vibe-flow:vibe-dispatch-fix | Re-dispatch to fix review criticals or CI failures |
| vibe-rebase | /vibe-flow:vibe-rebase <PR> | Resolve conflicts against updated main |
| vibe-status | /vibe-flow:vibe-status | Snapshot of active workspaces + PRs + inconsistencies |
| vibe-standup | /vibe-flow:vibe-standup | Periodic summary to configured channel |
| vibe-flow (meta) | /vibe-flow:vibe-flow <spec> | Full loop: plan → ship → review → merge → standup |
Invocation patterns
Claude Code will auto-discover the relevant skill from your prompt — you don’t have to memorize the exact name. But explicit invocations work too:
/vibe-flow:vibe-plan "Ship a dark mode toggle"
/vibe-flow:vibe-ship
/vibe-flow:vibe-review 123
Sub-skill composition
Higher-level skills invoke the specialists:
vibe-flow(meta) callsvibe-plan→vibe-ship→vibe-standupvibe-shipcallsvibe-link→vibe-review→vibe-mergeper issue, withvibe-dispatch-fixandvibe-rebasein the loop on failures
See waves for how the DAG drives parallel dispatch.