agentleFS
lgtm-hqlgtm-hq/ai-skills/skills/branch/SKILL.md

branch

Skill1 starsChanged 11 days agoMITView on GitHub

Start work on a new branch or worktree. Use when asked to start a new branch, new worktree, begin work on a feature/fix, or start fresh. Supports issue numbers and plain descriptions.

13 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use handoff.

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.
  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 4 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. 0 are common, 8 are distinctive, and 6 are very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 8

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Start work on a new git branch, optionally in a new worktree.

    line 11
  2. Very specific:

    If an issue has labels like bug → fix/, enhancement → feat/, documentation → docs/

    line 41
  3. Distinctive:

    If a description starts with a semantic prefix, use it

    line 43
  4. Very specific:

    Default to feat/ if unclear

    line 44
  5. Very specific:

    When asked to start a new branch (no --worktree / -w flag):

    line 61
  6. Distinctive:

    Run git status — if there are uncommitted changes, warn the user and stop

    line 64
  7. Distinctive:

    Do NOT stash or discard changes automatically

    line 65
  8. Very specific:

    If an issue number was given, fetch it: gh issue view <number> --json title,labels

    line 73
  9. Very specific:

    When --worktree or -w is specified:

    line 86
  10. Distinctive:

    Place as a sibling directory to the current repo

    line 98
  11. Distinctive:

    NEVER force-delete branches or worktrees

    line 122
  12. Distinctive:

    NEVER stash or discard uncommitted changes — always warn and stop

    line 123
  13. Very specific:

    Always branch from origin/main (freshly fetched)

    line 124
  14. Distinctive:

    If the branch name already exists, warn the user and ask what to do

    line 125

“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

Branch

Start work on a new git branch, optionally in a new worktree.

Arguments

Accepts one of the following as arguments:

  • Issue number: e.g., /branch 123 — fetches the issue title and derives the branch name
  • Description: e.g., /branch add shellcheck support — derives the branch name from the text
  • Worktree flag: append --worktree or -w to create a git worktree instead of a regular branch

Examples:

  • /branch 123 — branch from issue #123
  • /branch add dark mode toggle — branch from description
  • /branch 123 --worktree — worktree from issue #123
  • /branch fix login redirect -w — worktree from description

Branch Naming

Derive the branch name using this format:

<type>/<issue-number?>-<slug>
  • type: Infer from context — feat/, fix/, chore/, docs/, refactor/, perf/, test/, ci/
    • If an issue has labels like bug → fix/, enhancement → feat/, documentation → docs/
    • If a description starts with a semantic prefix, use it
    • Default to feat/ if unclear
  • issue-number: Include only if an issue number was provided
  • slug: Lowercase, hyphenated, max ~50 chars, derived from the issue title or description
    • Strip filler words when too long
    • e.g., "Add shellcheck support for shell scripts" → add-shellcheck-support

Examples:

  • Issue #123 titled "feat(cli): add watch mode" → feat/123-add-watch-mode
  • Issue #45 labeled bug, titled "Parser crashes on empty input" → fix/45-parser-crashes-on-empty-input
  • Description "add dark mode" → feat/add-dark-mode
  • Description "fix: resolve null pointer" → fix/resolve-null-pointer

Usage — Regular Branch

When asked to start a new branch (no --worktree / -w flag):

  1. Ensure clean state:
    • Run git status — if there are uncommitted changes, warn the user and stop
    • Do NOT stash or discard changes automatically
  2. Fetch latest:

    git fetch origin
  3. Resolve branch name:
    • If an issue number was given, fetch it: gh issue view <number> --json title,labels
    • Derive the branch name per the naming rules above
  4. Create and switch to the branch:

    git checkout -b <branch-name> origin/main
  5. Confirm — Print the branch name and a summary of what was done

Usage — Worktree

When --worktree or -w is specified:

  1. Ensure clean state:
    • Run git status — if there are uncommitted changes, warn the user and stop
  2. Fetch latest:

    git fetch origin
  3. Resolve branch name (same rules as above)
  4. Determine worktree path:
    • Place as a sibling directory to the current repo
    • Format: <repo-dir>-<slug> (without the type prefix)
    • e.g., if repo is at ~/Code/py-lintro and branch is feat/123-add-watch-mode:
      • Worktree path: ~/Code/py-lintro-123-add-watch-mode
    • e.g., if branch is fix/parser-crash:
      • Worktree path: ~/Code/py-lintro-parser-crash
  5. Create the worktree:

    git worktree add -b <branch-name> <worktree-path> origin/main
  6. Confirm — Print the worktree path, branch name, and how to navigate there:

    Created worktree at ~/Code/py-lintro-123-add-watch-mode
    Branch: feat/123-add-watch-mode (from origin/main)
    
    To start working:
      cd ~/Code/py-lintro-123-add-watch-mode

Important

  • NEVER force-delete branches or worktrees
  • NEVER stash or discard uncommitted changes — always warn and stop
  • Always branch from origin/main (freshly fetched)
  • If the branch name already exists, warn the user and ask what to do

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.