issue-driven-branching
Installation
SKILL.md
Branch Model
Use the issue system's generated branch names when available.
With Linear, copy the branch name from the issue instead of inventing one. The exact name is team-configured, for example:
alex-123-add-billing-settings
eng-456-create-api-endpoint
Do not depend on a specific naming convention. Depend on branch roles:
| Role | Source | Base branch |
|---|---|---|
| Release base | main or staging |
n/a |
| Parent feature branch | generated from the parent issue | staging if the team integrates there, otherwise main |
| Subissue branch | generated from the subissue | parent feature branch, or previous subissue branch if stacked |