SkillsAdd

inkblot-therapy/ai-skills · Archived

inkblot-branch-naming

Inkblot git branch naming convention. Use when creating a branch, checking out a feature/bugfix branch, naming a PR branch, or when the user asks to start work on a Jira ticket.

First seen Aug 21, 2026

Installation

$ npx skills add inkblot-therapy/ai-skills --skill inkblot-branch-naming
View on skills.sh ↗ GitHub repository ↗

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

inkblot-jira-ticket Same source · more installs
inkblot-therapy/ai-skills

Inkblot Jira ticket writing convention. Use whenever creating, drafting, editing, or reviewing …

33 installs
inkblot-commit-message Same source · more installs
inkblot-therapy/ai-skills

Inkblot git commit message convention. Use when writing a commit message, creating a git commit…

23 installs

Also in this package

Other skills from inkblot-therapy/ai-skills.

npx skills add inkblot-therapy/ai-skills
inkblot-jira-ticket 33 inkblot-commit-message 23

Browse all from inkblot-therapy/ai-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,105 B
  • docs SUMMARY.md 206 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 22 installs

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

  • pod2-2291-video-call-no-show
  • pod1-3452-company-renewal-dates
  • pod1-3459-coaching-duration-options

Do not (ticket work only)

  • Do not prefix the ticket ID (fix/pod2-2291-…, feat/…, feature/…, bf-…)
  • Do not shorten the project key (2-2291-…, 1-3452-…)
  • Do not use uppercase in the branch name (POD2-2291-…)
  • Do not put initials in the name (ji-pod1-2178-…)
  • Do not append the target env (-qa, -master)
  • Do not stack ticket IDs (pod2-2276-2277-2282-…) — use the primary ticket
  • Do not dump the full Jira title into the kebab

No ticket

No naming rule. hotfix/7.54.2, sync/…, qa-kuma, or any other name are all fine.

Why

  • Ticket-first, no type prefix: Jira and git grep need the key at the start. feat/ / fix/ only adds length.
  • Full key, lowercase: pod2-2291 is still the Jira key (linking works). Lowercase avoids macOS vs Linux case-sensitivity. 2-2291 is not a Jira key, so GitHub/Jira will not attach the branch.
  • Rule only when a ticket exists: Chores, syncs, and hotfixes without a ticket should not be blocked or renamed by the agent.
  • Short kebab: GitHub truncates long branch names; the ticket title already lives in Jira.