agentleFS
Sign inStart free
laz3rjenkinslaz3rjenkins/atomic-commits/skills/branch/SKILL.md

branch

Skill0 starsChanged 53 days agoMITView on GitHub

Create and switch to a new branch named after the task, e.g. feat/login-form or fix/empty-list-crash.

12 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use issue, test and 1 more.

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

  • 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

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    check git branch -a first.

    line 16
  2. Very specific:

    If the user wants to branch from somewhere other than the current HEAD ("from main"), run git switch -c <name> <base>.

    line 22

“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

Create a task branch

  1. Work out the task. Take it from the arguments. With no arguments, derive it from the uncommitted changes (git status, git diff HEAD). If there are no changes either, ask the user what the task is.
  2. Name the branch <type>/<short-kebab-description>, using the same types as Conventional Commits (feat, fix, docs, refactor, chore, ...).
    • lowercase ASCII, words joined with -, about 40 characters or less
    • transliterate or translate non-English input: "форма входа" becomes feat/login-form
    • check git branch -a first. If the repo already follows another convention (feature/..., ABC-123-...), follow that one instead.
  3. Create it from the current HEAD: git switch -c <name>. If the name is already taken, suggest a variant and ask. Don't overwrite the existing branch.
  4. Report the new branch name. If there were uncommitted changes, say they came along to the new branch. The branch isn't on the remote yet; the first /push publishes it.

If the user wants to branch from somewhere other than the current HEAD ("from main"), run git switch -c <name> <base>.

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