skills.rest
jcdendrite
jcdendriteCOMMUNITY
Explore all skills by this author →
GitHub

branch-creation

Create feature branches from the latest default branch tip using ticket-based naming.

4|1|Updated Mar 11, 2026
Search Tags:#git#workflow automation#pull requests#branch naming#repository hygiene#feature branches#plan files
One-click install
npx skills add https://github.com/jcdendrite/claude-config --skill branch-creation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: branch-creation
Source: https://github.com/jcdendrite/claude-config/tree/main/claude/.claude/skills/branch-creation
Command: npx skills add https://github.com/jcdendrite/claude-config --skill branch-creation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the chaos and hidden risk of starting feature work from a stale or improperly named branch, which leads to messy PR diffs and automation mismatches.

Core Features & Use Cases

  • Consistent, tracker-friendly branch naming: Uses the <TICKET-ID>/<topic-slug> convention when a ticket system exists, and falls back to <topic-slug> when it does not, avoiding non-standard user-prefixed defaults.
  • Branch-from-fresh-default guidance: Ensures branches originate from the current tip of the repo’s default branch (typically main), preventing “baggage” commits and dirty-state carryover.
  • Plan co-location rules: Commits any associated .claude/plans/<name>.md on the implementation feature branch so plans and code ship together in one PR.

Quick Start

Ask the AI to generate a branch name and the correct branching commands for a new feature based on the current default branch tip, including how to commit any related plan file to the same feature branch.

Frequently Asked Questions about branch-creation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the best way to name feature branches to keep pull requests clean?▼

To keep pull requests clean, name feature branches using a `<TICKET-ID>/<topic-slug>` convention when a ticket system exists, or `<topic-slug>` without one, rejecting non-standard user-prefixed defaults to maintain repository hygiene.

How do I create a feature branch from the latest main tip?▼

Create a feature branch from the latest main tip by standardizing branch creation to always originate from the current default branch tip, preventing "baggage" commits and dirty-state carryover from polluting your pull request diffs.

Why does my feature branch include unrelated commits in the pull request diff?▼

Your feature branch includes unrelated commits because it was not branched from the latest default branch tip, causing dirty-state carryover and "baggage" commits that pollute the pull request diff.

How do I co-locate plan files with feature branch commits?▼

To co-locate plan files with feature branch commits, commit any associated `.claude/plans/<name>.md` plan file directly onto the implementation feature branch so plans and code ship together in one pull request.

When should I not use automated branch naming conventions?▼

You should not use automated branch naming conventions for syncing existing branches or force-pushing cases, as this workflow applies specifically to creating implementation work branches and committing associated plan files.

Related Skills

Explore More Software Engineering Skills→
adamfilliadamfilli
11

rebase

Rebase the current Git branch onto the latest origin/main branch.

Community
Intermediate
VYRE-StudiosVYRE-Studios

commit-push-pr

Commit staged changes, push the branch, and open a pull request via GitHub CLI.

Official
Intermediate
etylsarinetylsarin
59

git-workflow

Enforce feature-branch pull request workflows and prevent direct commits to main.

Community
Intermediate
kristofferrembackkristofferremback
2

commit

Create conventional git commit messages from staged changes with Linear ticket IDs.

Community
Basic