create-branch
Create a feature branch following project naming conventions. Use when starting work on a ticket, after understanding the scope, or when the agent needs to branch off main for new work.
Best use case
create-branch is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Create a feature branch following project naming conventions. Use when starting work on a ticket, after understanding the scope, or when the agent needs to branch off main for new work.
Teams using create-branch should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/create-branch/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How create-branch Compares
| Feature / Agent | create-branch | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Create a feature branch following project naming conventions. Use when starting work on a ticket, after understanding the scope, or when the agent needs to branch off main for new work.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Create Branch Create a feature branch following the `<nickname>/<descriptive-branch-name>` convention used in this repository. ## Steps ### 1. Detect the user's nickname Resolve the nickname using the first approach that succeeds: 1. **Memory** — check if a stored memory already contains the user's nickname. 2. **`make nickname`** — outputs the local part of `git config user.email` (before `@`). 3. **Ask** — if neither works, ask the user. Once resolved, save the nickname to memory for future conversations. ### 2. Derive a descriptive branch name Combine the ticket ID (if available) and a short slug describing the change: - Use lowercase kebab-case: `fix-auth-timeout`, `add-mcp-tool-list` - Keep it under 50 characters - If a YouTrack ticket is known (e.g., `DBA-123`), prefer including it: `<nickname>/DBA-123-fix-auth-timeout` ### 3. Ensure a clean starting point - Fetch latest: `git fetch origin` - If the working tree has uncommitted changes, warn the user and ask whether to stash or proceed. - Branch from `main` (or the base branch the user specifies): `git checkout -b <nickname>/<branch-name> origin/main` ### 4. Confirm Report the created branch name to the user. ## Guardrails - Never create branches directly on `main` — always branch _from_ main. - Never silently discard uncommitted changes. - If the user is already on a feature branch, ask before switching.
Related Skills
create-pr
Stage, commit, push, and open a GitHub PR following project conventions. Use when code is ready to ship.
write-tests
Write or update unit tests for changed code, following project conventions and ensuring coverage meets the 80% threshold.
update-pr
Stage, commit, and push follow-up changes to an existing feature branch or PR. Use for quick iterations.
setup-environment
Set up or verify the local development environment. Use when starting work in a fresh clone or new machine, when commands fail with missing dependencies or broken imports, or before running `make check`/`make test` for the first time in a session.
review-architecture
Review architecture quality, maintainability, and developer experience.
make-yt-issue
Ensure a YouTrack issue exists before starting work. Validates existing tickets or creates new ones.
local-code-review
Review local code changes for correctness, regressions, missing tests, and Databao-specific risks.
eval-skills
Run structured evaluations on skills to measure quality and track improvements.
check-pr-comments
Fetch unresolved PR review threads, triage them, implement fixes, validate, reply in-thread, and resolve.
check-coverage
Run test coverage measurement, analyze results, and fix gaps when coverage falls below the 80% threshold.
autosteer
Run the full development pipeline autonomously without pausing between phases. Stops only on quality-gate failures.
review-current-branch
シニアソフトウェアエンジニアとして現在のブランチのプルリクエストをレビューする