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>
  1. Full key, lowercase, one primary ticket (e.g. pod2-2291, not 2-2291)
  2. kebab is lowercase, 3–5 words — the change, not the ticket title
  3. Keep the whole name short enough to read in GitHub’s branch list (~50 characters)

Examples

Installs
28
First Seen
Aug 21, 2026
inkblot-branch-naming — inkblot-therapy/ai-skills