new-branch

Original：🇺🇸 English

Translated

Prepare local GitHub issue branches from the repository default branch using GitHub-style issue branch names. Use when starting issue-linked work, when the user says new branch for an issue, or when an agent must move onto the correct issue branch before implementation.

3installs

Sourcepatinaproject/skills

Added on2026-05-19

NPX Install

npx skill4agent add patinaproject/skills new-branch

SKILL.md Content

View Translation Comparison →

New Branch

Quick Start

Given an issue reference, follow workflows/issue-branch.md.

Example: issue

#42

titled

Let agents use GitHub more ergonomically

becomes local branch

42-let-agents-use-github-more-ergonomically

.

The skill creates or switches to the local issue branch only. It does not install dependencies, push, commit, create a pull request, or start implementation work.

Workflow

Read the repository guidance first, especially branch and GitHub rules.
Resolve the issue in the current working directory's default
```
gh
```
repository.
Compute the branch name as
```
<issue-number>-<kebab-title>
```
, matching GitHub's issue branch suggestion.
Refuse to switch branches when the worktree has uncommitted changes.
Fetch the repository default branch from
```
origin
```
.
Create the branch from
```
origin/<default-branch>
```
, switch to it, or warn before leaving a different issue branch.
Report the branch and base SHA.

Guardrails

Stay in the current
```
gh
```
repository; do not accept cross-repo flags.
Never hardcode
```
main
```
; resolve the default branch through
```
gh repo view
```
.
Keep empty issue branches local.
Ask before switching away from a different issue branch.
Stop on rebase conflicts and surface the manual resolution steps.