Agent skill

New Branch from Main

Creates a Git branch from an up-to-date main using a type-prefixed, kebab-case name such as feat or fix, and keeps work off main.

Apache-2.0Auto-check passedDevelopment

Install New Branch from Main

skills CLI

$ npx skills add EverMind-AI/EverOS --skill new-branch -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install EverMind-AI/EverOS new-branch --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/EverMind-AI/EverOS.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/new-branch .claude/skills/new-branch && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "new-branch" agent skill from https://github.com/EverMind-AI/EverOS/tree/main/.claude/skills/new-branch into .claude/skills/new-branch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "new-branch", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/EverMind-AI/EverOS/tree/main/.claude/skills/new-branch

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add EverMind-AI/EverOS --skill new-branch -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install EverMind-AI/EverOS new-branch --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/EverMind-AI/EverOS.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/new-branch .agents/skills/new-branch && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "new-branch" agent skill from https://github.com/EverMind-AI/EverOS/tree/main/.claude/skills/new-branch into .agents/skills/new-branch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "new-branch", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add EverMind-AI/EverOS --skill new-branch -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install EverMind-AI/EverOS new-branch --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/EverMind-AI/EverOS.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/new-branch .cursor/skills/new-branch && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "new-branch" agent skill from https://github.com/EverMind-AI/EverOS/tree/main/.claude/skills/new-branch into .cursor/skills/new-branch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "new-branch", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/EverMind-AI/EverOS.git --path .claude/skills/new-branch

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add EverMind-AI/EverOS --skill new-branch -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install EverMind-AI/EverOS new-branch --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/EverMind-AI/EverOS.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/new-branch .gemini/skills/new-branch && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "new-branch" agent skill from https://github.com/EverMind-AI/EverOS/tree/main/.claude/skills/new-branch into .gemini/skills/new-branch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "new-branch", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install EverMind-AI/EverOS new-branch

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add EverMind-AI/EverOS --skill new-branch -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/EverMind-AI/EverOS.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/new-branch .github/skills/new-branch && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "new-branch" agent skill from https://github.com/EverMind-AI/EverOS/tree/main/.claude/skills/new-branch into .github/skills/new-branch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "new-branch", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add EverMind-AI/EverOS --skill new-branch -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install EverMind-AI/EverOS new-branch --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/EverMind-AI/EverOS.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/new-branch .opencode/skills/new-branch && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "new-branch" agent skill from https://github.com/EverMind-AI/EverOS/tree/main/.claude/skills/new-branch into .opencode/skills/new-branch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "new-branch", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: new-branch
GitHub stars: 13k
Token cost: ~273 tokens
SKILL.md length: 76 words
Files: 1
Skills in repo: 5
Repo updated: Oct 10, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Creates a Git branch from an up-to-date main using a type-prefixed, kebab-case name such as feat or fix, and keeps work off main.

Works in 4 steps: Ask (or infer) the change type: feat,… → Update main first → Create the branch with a kebab-case slug → …
Starting work on a new feature or bug fix
SKILL.md covers Branch model, Steps and Naming
Calls git

What it does

The /new-branch command cuts a new branch for a GitHub repository under a simple branch model: main is the default and protected branch, and work happens on prefixed branches such as feat for features and fix for bug fixes. The agent asks for or infers the change type from feat, fix, docs, ci, chore and refactor.

It then checks out main, pulls with a fast-forward-only update, and creates the branch from a type prefix, a slash and a short slug that is lowercase, hyphen-separated and free of spaces. Examples include feat/add-agentic-rerank and fix/empty-profile-crash. The branch stays scoped to one purpose and goes back to main through a pull request, and the skill states that nothing is ever committed directly to main.

When your agent uses it

Starting work on a new feature or bug fix
Naming a branch consistently with the project convention
Making sure a branch starts from the latest main
Preparing changes for a pull request instead of committing to main

Example prompts

“Create a branch for fixing the empty profile crash.”
“Start a new feature branch for adding rerank support.”
“Cut a docs branch for the quickstart config page.”

Requirements

git, with a remote main branch to pull from

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

Ask (or infer) the change type: feat, fix, docs, ci, chore, or
Update main first
Create the branch with a kebab-case slug
Keep the branch scoped to one purpose and open a pull request back to

What it can do on your machine

Read from SKILL.md and the folder at commit fcd41b5. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

New Branch from Main loads about 273 tokens when it runs. Until then it costs about 20 tokens; SKILL.md has 76 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~20
When it runs · the whole SKILL.md, loaded when a task matches: ~273

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from EverMind-AI/EverOS at commit fcd41b5, republished under its Apache-2.0 licence (© EverMind-AI). 76 words, ~273 tokens.

Download SKILL.mdSave it as .claude/skills/new-branch/SKILL.md (or your agent's skills folder).

name: new-branch
description: Create a GitHub branch from main with the project naming convention

/new-branch

Cut a new branch for the GitHub repository.

Branch model

main       = default and protected branch
feat/*     = feature work
fix/*      = bug fixes
docs/*     = documentation-only changes
ci/*       = CI, build, and developer-experience changes
chore/*    = repository maintenance
refactor/* = behavior-preserving code structure changes

Steps

Ask (or infer) the change type: feat, fix, docs, ci, chore, or refactor.
Update main first:
bash
```
git checkout main
git pull --ff-only
```
Create the branch with a kebab-case slug:
bash
```
git checkout -b <type>/<short-slug>
```
Keep the branch scoped to one purpose and open a pull request back to main.

Naming

feat/add-agentic-rerank, fix/empty-profile-crash, docs/quickstart-config, ci/check-github-docs.
Lowercase, hyphen-separated, no spaces, concise.

Never commit directly to main — always use a branch and pull request.

Files

Just SKILL.md in .claude/skills/new-branch of EverMind-AI/EverOS.

Open the folder on GitHubat commit fcd41b5

Compare with similar skills

New Branch from Main next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

New Branch from Main compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
New Branch from Main this skillEverMind-AI/EverOS	13k	—	~273	Automated safety check: Pass	Apache-2.0	today
Contributor-First PR MergeHKUDS/OpenHarness	16k	1 repos	~847	Automated safety check: Pass	MIT	4 mo ago
Create Pull Requestcline/cline	70k	1 repos	~1.6k	Automated safety check: Pass	Apache-2.0	today
Release Bumpjamiepine/voicebox	57k	—	~1.1k	Automated safety check: Pass	MIT	3 days ago
Create Pull Request with Work Item IDmakeplane/plane	61k	—	~824	Automated safety check: Pass	AGPL-3.0	yesterday
Creating Description For Gh PRredis/jedis	12k	—	~838	Automated safety check: Pass	MIT	today

Similar skills

Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
16k GitHub starsUsed in 1 repo~847 tokens
DevelopmentAuto-check passed
Create Pull Request
cline/cline
Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.
70k GitHub starsUsed in 1 repo~1.6k tokens
DevelopmentAuto-check passed
Release Bump
jamiepine/voicebox
Ends a release cycle by moving the Unreleased changelog notes under a dated version heading, bumping version files with bumpversion and tagging the commit.
57k GitHub stars~1.1k tokensUpdated 3 days ago
DevelopmentAuto-check passed
Create Pull Request with Work Item ID
makeplane/plane
Opens a pull request for the current branch using the repo's template, a work item ID in the title and a description filled in from the actual diff.
61k GitHub stars~824 tokensUpdated yesterday
DevelopmentAuto-check passed
Creating Description For Gh PR
redis/jedis
Official
Generate a clear, concise GitHub PR title and description from the diff between two local git branches, and save it to prDescription.md in the repo root.
12k GitHub stars~838 tokensUpdated today
DevelopmentAuto-check passed
Pascal Editor PR Opener
pascalorg/editor
Opens or refreshes a pull request on pascalorg/editor from the current branch, describing only what the branch's commits and diff actually contain.
25k GitHub stars~619 tokensUpdated today
DevelopmentAuto-check passed

Questions about New Branch from Main

What does New Branch from Main do?

Creates a Git branch from an up-to-date main using a type-prefixed, kebab-case name such as feat or fix, and keeps work off main. The /new-branch command cuts a new branch for a GitHub repository under a simple branch model: main is the default and protected branch, and work happens on prefixed branches such as feat for features and fix for bug fixes. The agent asks for or infers the change type from feat, fix, docs, ci, chore and refactor.

When should I use New Branch from Main?

New Branch from Main fits situations like: starting work on a new feature or bug fix; naming a branch consistently with the project convention; making sure a branch starts from the latest main; preparing changes for a pull request instead of committing to main.

How do I install New Branch from Main in Claude Code?

Run `npx skills add EverMind-AI/EverOS --skill new-branch -a claude-code`. Or copy the skill folder (.claude/skills/new-branch in EverMind-AI/EverOS) into .claude/skills/new-branch in your project. Claude Code loads it when a task matches its description.

How do I install New Branch from Main in Codex?

Run `npx skills add EverMind-AI/EverOS --skill new-branch -a codex`. Or copy the skill folder (.claude/skills/new-branch in EverMind-AI/EverOS) into .agents/skills/new-branch in your project. Codex loads it when a task matches its description.

Can I use New Branch from Main in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add EverMind-AI/EverOS --skill new-branch -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/new-branch, .gemini/skills/new-branch, .github/skills/new-branch and .opencode/skills/new-branch in your project.

What does New Branch from Main need to run?

Going by SKILL.md and its folder, New Branch from Main needs the command-line tools its instructions call (git). Our summary lists: git, with a remote main branch to pull from.

Does New Branch from Main access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is New Branch from Main safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does New Branch from Main use?

New Branch from Main is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does New Branch from Main use?

About 273 tokens (SKILL.md is roughly 1.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to New Branch from Main?

Skills that share tags, products or a category with New Branch from Main: Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Create Pull Request (cline/cline, 70k stars), Release Bump (jamiepine/voicebox, 57k stars) and Create Pull Request with Work Item ID (makeplane/plane, 61k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains New Branch from Main?

EverMind-AI (a GitHub organization) maintains it in EverMind-AI/EverOS, which has 13,393 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 10, 2026.

Source: EverMind-AI/EverOS on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

New Branch from Main

Install New Branch from Main

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

/new-branch

Branch model

Steps

Naming

Files

Compare with similar skills

Similar skills

Contributor-First PR Merge

Create Pull Request

Release Bump

Create Pull Request with Work Item ID

Creating Description For Gh PR

Pascal Editor PR Opener

More from EverMind-AI/EverOS

Add Memory Kind

Conventional Commit Writer

EverOS Release Workflow

Pull Request with Project Template

Questions about New Branch from Main

Install New Branch from Main

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

/new-branch

Branch model

Steps

Naming

Files

Compare with similar skills

Similar skills

More from EverMind-AI/EverOS

Related

Questions about New Branch from Main