inkblot-branch-naming
Installation
SKILL.md
Inkblot branch naming
This convention is only required when the work has a Jira ticket. If there is no ticket, do not invent a prefix, do not ask for a ticket, and do not restrict the name.
Ticket work (required)
The branch starts with the full Jira key, lowercase. Do not add feat/ / fix/ / feature/ type prefixes.
<ticket-id>-<short-kebab>
- Full key, lowercase, one primary ticket (e.g.
pod2-2291, not2-2291) - kebab is lowercase, 3–5 words — the change, not the ticket title
- Keep the whole name short enough to read in GitHub’s branch list (~50 characters)