branching

branching is a skill for Claude Code from nguyenthanhtat/screen1-claude. It costs 0 tokens per session (4,155 once invoked), scanned A, original, MIT.

A guide to managing Git branches, which are separate lines of work in a code project.

In plain words
What is it for?
Creating, switching, merging, rebasing, naming, and deleting branches.
Why use it?
It helps keep feature work and fixes separate, combine changes safely, and maintain a readable project history.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the screen1-skills plugin — 46 skills shipped together

Good fit Creating, switching, merging, rebasing, naming, and deleting branches.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nguyenthanhtat/screen1-claude/branching
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add nguyenthanhtat/screen1-claude --skill branching
Clone the repo
git clone --depth 1 https://github.com/nguyenthanhtat/screen1-claude

Made for: Claude Code.

Or install screen1-skills, the plugin that ships this one along with the rest of its 46 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for branching

README.md
[![agentmods](https://agentmods.dev/badge/skills/nguyenthanhtat/screen1-claude/branching/github.svg)](https://agentmods.dev/skills/nguyenthanhtat/screen1-claude/branching)
Your own site
<a href="https://agentmods.dev/skills/nguyenthanhtat/screen1-claude/branching"><img src="https://agentmods.dev/badge/skills/nguyenthanhtat/screen1-claude/branching/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for branching

Your own site · 80×15
<a href="https://agentmods.dev/skills/nguyenthanhtat/screen1-claude/branching"><img src="https://agentmods.dev/badge/skills/nguyenthanhtat/screen1-claude/branching.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,155 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.04155
Opus 5 $0.00000 $0.02077
Sonnet 5 $0.00000 $0.00831
Haiku 4.5 $0.00000 $0.00415

Measured 10d ago against content hash 7774f40ed822, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

branching scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/git/branching/SKILL.md · 773 lines

How it starts

The opening of the file, as written. The whole thing — 773 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Git Branching

Parent Skill: /git Path: /git/branching

Purpose

Master branch management including creating, merging, rebasing, and organizing branches for clean workflows. Learn merge strategies, interactive rebase, and branch naming conventions.

When to Use

Trigger automatically when:

  • User mentions: branch, checkout, merge, rebase, switch, delete branch
  • Creating new features
  • Integrating changes
  • Cleaning up branch history
  • Branch organization questions

Chat commands:

/git/branching create new feature branch
/git/branching merge feature into main
/git/branching rebase my branch on main
/git/branching delete old branches
/git/branching interactive rebase to clean history

Requirements

Verification

# Check current branch
git branch --show-current

# List all branches
git branch -a

# Check if branch exists
git rev-parse --verify feature-branch

Critical Rules


Branching Workflow

main (production)
  ├── feature/user-auth
  ├── feature/dashboard
  └── fix/login-bug

Workflow:
1. Create branch from main
2. Make commits on branch
3. Merge or rebase to integrate
4. Delete branch after merge

Patterns

Pattern 1: Create and Switch Branches

Problem: Start working on a new feature without affecting main code

# ❌ BAD: Old syntax, easy to make mistakes
git branch feature-login
git checkout feature-login  # Two commands

# Or worse:
git checkout -b feature-login  # Creates locally only

# ✅ GOOD: Modern syntax (Git 2.23+)
git switch -c feature-login
# or
git switch --create feature-login

# ✅ BETTER: Create from specific branch
git switch -c feature-login main  # Create from main

# Create from remote branch
git switch -c local-name origin/remote-branch

Read the full file on GitHub · 773 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 773 lines · 0 tokens per session scan A 7774f40ed822

Subscribe to this mod's changes

branching is a skill published in the GitHub repository nguyenthanhtat/screen1-claude (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,155 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

prowler-commit

Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.

prowler-cloud/prowler · 33 tokens

gh-auth-isolation

Safely manage multiple GitHub identities (EMU + personal) in agent workflows.

github/gh-aw · 20 tokens

comet-github

A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.

rpamis/comet · 72 tokens

github-skill

Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.

zeenie-ai/OpenCompany · 51 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens

nvca-chart-release

Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.

NVIDIA/nvcf · 61 tokens