agentleFS
Sign inStart free
ahonnahonn/dotfiles/.claude/skills/branch/SKILL.md

branch

Skill62 starsChanged 2 months agoMITView on GitHub

Create or name a Git branch using the user's conventional-commit naming rules.

12 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use issue and test.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AWSSkill

    issue

    Implement a GitHub issue end-to-end — branch, code, test, docs, and commit.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    test

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the user only asks for a branch name, propose the name without changing repository state.

    line 28
  2. Very specific:

    Create with git switch -c <name> <verified-base>.

    line 33

“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Conventional Branch Names

Branch names use the same type vocabulary as conventional commits:

<type>/<short-kebab-description>

Examples: feat/user-auth, fix/login-crash, refactor/api-client, chore/update-deps.

Rules

  1. Type — the conventional-commit type the dominant commit on this branch would have: feat, fix, refactor, perf, docs, test, build, ci, chore, revert.
  2. Description — 2–4 words, kebab-case, specific: what the branch delivers, not how. Lowercase only, no spaces.
  3. Ticket IDs — if the work has a ticket, put its ID after the type: feat/lin-123-user-auth.
  4. No agent-branded prefixes — never codex/..., claude/..., or agent/.... The branch describes the work, not the tool that wrote it.
  5. Base — use the user's requested starting point. Otherwise prefer the up-to-date default branch, except when the task clearly continues current branch work. Inspect repository state before choosing it; preserve uncommitted work.

Procedure

If the user only asks for a branch name, propose the name without changing repository state. Use the creation steps when creating a branch is within the requested work.

  1. Derive type and description from the requested work (or "$ARGUMENTS" if provided).
  2. Validate: git check-ref-format --branch <name>.
  3. Inspect git status --short --branch and the available refs. Resolve the requested base; if a fresh remote base is needed, fetch that ref and verify it before proceeding. Do not assume the current checkout is the default branch or up to date.
  4. Create with git switch -c <name> <verified-base>; omit the base only when intentionally branching from current HEAD. If switching would disturb unrelated edits, use an isolated worktree when appropriate or ask for the unresolved starting-point decision. Do not stash, discard, reset, or overwrite work implicitly.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free