Skip to main content

/

/

Stats

Actions

Tags

Stats

Actions

Tags

ClaudePluginHub

Community directory for discovering and installing Claude Code plugins.

Find plugins for your stack

Instant recommendations from real install data.

Product

Browse Plugins
Marketplaces
Pricing
About
Contact

Resources

Learning Center
Blog
Weekly Digest
Claude Code Docs
Plugin Guide
Plugin Reference
Plugin Marketplaces

Community

Browse on GitHub
Get Support

Legal

Terms of Service
Privacy Policy

Browse · Plugins · Top Plugins · Marketplaces · Components · Technologies · Skills · Agents · Commands · Hooks · MCP Servers · LSP Servers · Output Styles · Themes · Monitors

Categories · Productivity · Development · Testing · Deployment · Security · Documentation · Data · Utilities

© 2025 ClaudePluginHub

Community Maintained · Not affiliated with Anthropic

ClaudePluginHub

ClaudePluginHub

Tools Learn Pricing

Search everything...

branch | blueprint

Home
Skills
blueprint
branch

Skill

branch

Creates traceable Git branches for current tasks using ticket IDs or short summaries (e.g., <ticket-id>-<short-kebab-summary>). Inspects git status, safely switches/creates, reports uncommitted work.

Popularity

Stars

137

Forks

23

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/blueprint:branch <branch-name or task reference>

User invocable

Model invocable

Inline context

Default effort

Argument hint<branch-name or task reference>

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

Create a traceable Git branch for the current task.

SKILL.md

28 lines · ~287 tokens

Stats

LanguageShell

Stars137

Forks23

MaintenanceExcellent

Last CommitJun 7, 2026

Actions

View Source View Plugin View on GitHub View README

Tags

Stats

LanguageShell

Stars137

Forks23

MaintenanceExcellent

Last CommitJun 7, 2026

Actions

View Source View Plugin View on GitHub View README

Tags

Branch

Create a traceable Git branch for the current task.

Workflow

Inspect the current Git branch, git status, and available task context.
Identify the ticket ID when the work comes from an issue tracker. If the task has a ticket but no visible ID, ask for it.
Use the user's branch name if provided; if work from an issue tracker omits the ticket ID, ask before creating it.
Otherwise derive <ticket-id>-<short-kebab-summary> when there is a ticket ID, or <short-kebab-summary> when there is not.
Preserve an obvious repo prefix such as feature/ only if the ticket ID remains visible.
If the branch already exists, switch to it. Otherwise, create and switch to it.
Report the branch name and any uncommitted work that was already present.

Rules

Stop if the working tree state makes switching branches unsafe.
Do not overwrite or discard uncommitted work.
Include the ticket ID for work from an issue tracker.
Do not invent ticket IDs.

$

npx claudepluginhub owainlewis/blueprint --plugin blueprint

Similar Skills

create-branch

850

Creates git branches following Sentry naming conventions by analyzing changes and classifying branch types. Useful for standardizing branch creation.

View create-branch

create-branch

42.7k

Creates git branches following Sentry naming conventions. Automatically determines branch type and description from arguments or local diff. Useful when starting new work.

agentic-awesome-skills

View create-branch

Branch

64

Creates and switches to a new conventionally named branch, preserving all local changes without committing or pushing. Derives name from inline description, conversation context, or git diffs.

1 file