Analyzes git changes and creates a new branch with an appropriate name following naming conventions. Use when creating new branches from current changes.
Analyzes git changes and creates a new branch with an appropriate name following naming conventions.
npx claudepluginhub kkhys/claude-code-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Analyze git changes (commits and uncommitted changes) to determine appropriate branch name, then create the branch.
<type>/<description>
| Type | Usage |
|---|---|
feature/ | New feature |
fix/ | Bug fix |
refactor/ | Refactoring |
docs/ | Documentation |
style/ | Code style / design |
chore/ | Miscellaneous / config |
add-, update-, remove-, fix-)feature/add-contact-form
fix/spelling-error-in-footer
refactor/user-controller
docs/update-readme
chore/update-dependencies
Run these commands to understand changes:
# Check current branch
git branch --show-current
# View uncommitted changes
git status --short
# View diff of uncommitted changes
git diff --stat
# View staged changes
git diff --cached --stat
# View recent commits (if on a feature branch)
git log --oneline -10
Based on changes:
| Changes | Type |
|---|---|
| New files, new functionality | feature/ |
| Bug corrections | fix/ |
| Code restructuring without behavior change | refactor/ |
| README, comments, docs | docs/ |
| Formatting, CSS | style/ |
| Config, dependencies, tooling | chore/ |
Once you've determined the appropriate branch name:
git checkout -b <type>/<description>
Present the result in this format:
Created branch: <type>/<description>
Reason: <brief explanation of why this name fits the changes>
Avoid these names:
# Too vague
test
fix1
branch2
update
changes
# Missing type prefix
add-login
user-feature
# Wrong case
feature/Add_Login
feature/addLogin
Changes include new functionality?
├─ Yes → feature/
└─ No
├─ Fixing a bug? → fix/
├─ Only docs/README? → docs/
├─ Only formatting/style? → style/
├─ Restructuring code? → refactor/
└─ Config/tooling? → chore/
If changes are ambiguous, ask user:
Then suggest 2-3 options with explanations and create the branch with user's choice.
Search, retrieve, and install Agent Skills from the prompts.chat registry using MCP tools. Use when the user asks to find skills, browse skill catalogs, install a skill for Claude, or extend Claude's capabilities with reusable AI agent components.
Activates when the user asks about AI prompts, needs prompt templates, wants to search for prompts, or mentions prompts.chat. Use for discovering, retrieving, and improving prompts.
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.