Manage Git Branches
Create, track, switch, sync, and clean up Git branches. Covers naming conventions, safe branch switching with stash, upstream synchronization, and pruning merged branches. Use when starting work on a new feature or bug fix, switching between tasks on different branches, keeping a feature branch up to date with main, or cleaning up branches after merging pull requests.
Install
npx skills add pjt222/agent-almanac --skill manage-git-branchesgit clone --depth 1 https://github.com/pjt222/agent-almanac.git /tmp/agent-almanac
mkdir -p ~/.claude/skills
cp -r /tmp/agent-almanac/i18n/caveman-lite/skills/manage-git-branches ~/.claude/skills/manage-git-branchesPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Manage Git Branches Create, switch, sync, and clean up branches following consistent naming conventions. ## When to Use - Starting work on a new feature or bug fix - Switching between tasks on different branches - Keeping a feature branch up to date with main - Cleaning up branches after merging pull requests - Listing and inspecting branches ## Inputs - **Required**: Repository with at least one commit - **Optional**: Branch naming convention (default: `type/description`) - **Optional**: Base branch for new branches (default: `main`) - **Optional**: Remote name (default: `origin`) ## Procedure ### Step 1: Create a Feature Branch Use a consistent naming convention: | Prefix | Purpose | Example | |---|---|---| | `feature/` | New functionality | `feature/add-weighted-mean` | | `fix/` | Bug fix | `fix/null-pointer-in-parser` | | `docs/` | Documentation | `docs/update-api-reference` | | `refactor/` | Code restructuring | `refactor/extract-validation` | | `chore/` | Maintenance | `chore/update-dependencies` | | `test/` | Test additions | `test/add-edge-case-coverage` | ```bash # Create and switch to a new branch from main git checkout -b feature/add-weighted-mean main # Or using the newer switch command git switch -c feature/add-weighted-mean main ``` **Got:** New branch created and checked out. `git branch` shows the new branch with an asterisk.
Details
- Skill name
manage-git-branches- Repository
- pjt222/agent-almanac
- Path
i18n/caveman-lite/skills/manage-git-branches/SKILL.md- License
- MIT
- Repo updated
- 18 November 2026
- Listed in
- BehiSecc/awesome-claude-skills
FAQ
What does the Manage Git Branches skill do?
Create, track, switch, sync, and clean up Git branches. Covers naming conventions, safe branch switching with stash, upstream synchronization, and pruning merged branches. Use when starting work on a new feature or bug fix, switching between tasks on different branches, keeping a feature branch up to date with main, or cleaning up branches after merging pull requests.
How do I install the Manage Git Branches skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add pjt222/agent-almanac --skill manage-git-branches. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Manage Git Branches popular?
It lives in pjt222/agent-almanac, which has 45 GitHub stars and 4 forks, and is included in 1 curated skill list.
Related skills
Adapt Architecture
45pjt222/agent-almanac
Execute structural metamorphosis using strangler fig migration, chrysalis phases, and interface preservation. Covers transformation planning, parallel running, progressive cutover, rollback design, and post-metamorphosis stabilization for system architecture evolution. Use when assess-form has classified the system as READY for transformation, when migrating from monolith to microservices, when replacing a core subsystem while dependents continue operating, or when any architectural change must be gradual rather than big-bang.
Adaptic
45pjt222/agent-almanac
Master skill composing the 5-step synoptic cycle for panoramic synthesis across multiple domains. Orchestrates meditate, expand-awareness, observe, awareness, integrate-gestalt, and express-insight into a coherent process that produces unified understanding rather than sequential compromise. Use when a problem genuinely spans 3+ domains and the interactions between domains matter more than depth in any one, when sequential analysis feels like compromise rather than integration, or before major architectural decisions affecting multiple stakeholders.
Add Puzzle Type
45pjt222/agent-almanac
Scaffold a new puzzle type across all 10+ pipeline integration points in jigsawR. Creates the core puzzle module, wires it into the unified pipeline (generation, positioning, rendering, adjacency), adds ggpuzzle geom/stat layers, updates DESCRIPTION and config.yml, extends the Shiny app, and creates a comprehensive test suite. Use when adding a completely new puzzle type to the package or following the 10-point integration checklist to ensure nothing is missed end-to-end.
Polish Claw Project
45pjt222/agent-almanac
Contribute to OpenClaw ecosystem projects (OpenClaw, NemoClaw, NanoClaw) through a structured 9-step workflow: target verification, codebase exploration, parallel audit, finding cross-reference, and pull request creation. Emphasizes false positive prevention and project convention adherence.
Manage Changelog
45pjt222/agent-almanac
Maintain a changelog following Keep a Changelog format. Covers entry categorization (Added, Changed, Deprecated, Removed, Fixed, Security), version section management, and unreleased tracking. Use when starting a new project that needs a changelog, adding entries after completing features or fixes, preparing a release by promoting Unreleased entries to a versioned section, or converting a free-form changelog to Keep a Changelog format.
Redact for Public Disclosure
45pjt222/agent-almanac
Redact reverse-engineering findings for public disclosure while preserving methodology, generalizable patterns, and teaching value. Covers the private-vs-public repo split, deny-list pattern maintenance, orphan-commit publish pattern that prevents `git log` leaks, category-based redaction calibration (methodology/pattern/version-finding/internal), and the `check-redaction.sh`-style CI gate that blocks merges when a deny-listed pattern appears. Use when publishing findings about a CLI harness you don't own, when preparing upstream proposals to an unrelated project, or when archiving a private r
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.