Git Branch Names and Conventional PR Titles
Branch name and Conventional Commits PR title that match your repo's convention, plus safe commands to create the branch and draft PR.
Before & after
Same prompt, same agent — the only difference is the skill.
When creating a new branch for your work, it's good practice to use a descriptive name. Many teams follow conventions like starting with the issue number or a prefix that describes the type of work. You might use something like 'feature' or 'fix' as a prefix. The branch name should be easy to remember and understand at a glance. After creating the branch, you'll want to commit your work regularly and eventually open a pull request. Good git hygiene helps with code review and keeps the repository organized.
GENERATED BRANCH AND PR: BRANCH CHECKOUT COMMAND git checkout -b feature/2fa-login-implementation DRAFT PR CREATED Title: Add two-factor authentication to login flow Body: Description Implements SMS and TOTP-based 2FA option during login. Users can choose method in account settings and will be prompted at next login. Changes: - New AuthService.verifyTwoFactorCode() method - TwoFactorSetup component (SMS + TOTP selection) - Login form updated to support 2FA prompt - Database migrations for user_2fa_methods table Type: Feature Related: issue-487 Checklist: - [ ] Tests written for 2FA validation - [ ] SMS provider integration tested (Twilio sandbox) - [ ] TOTP secret generation verified - [ ] User onboarding docs updated CONVENTION APPLIED Prefix: feature/ (indicates new capability) Subject: verb-noun-context (2fa-login-implementation) Length: 40 characters, all-lowercase, hyphens NEXT STEPS 1. Commit code to feature/2fa-login-implementation 2. Open PR from draft (ready for review when tests pass) 3. Reference related issues with GitHub mention syntax
About this skill
Your PR title fails the commitlint check again. Jira doesn't link the branch. A refactor went out labeled feat and bumped the minor version. This skill names branches and PR titles from the convention your repo already uses. It picks the commit type by what the change does for users, and it sets up the branch and draft PR without the usual empty-branch and --fill mistakes.
What it does
- Reads your recent branches, commit log, and commitlint or semantic-PR config, then copies the separator, ticket casing, and scope vocabulary already in use
- Chooses feat, fix, perf, refactor, build, ci, docs, or chore based on user-visible effect, and explains how that choice affects semantic-release version bumps
- Places ticket keys so Jira or Linear can auto-link the branch, and never makes up a ticket number or scope
- Checks names against git ref rules, length limits for preview URLs and CI, and conflicts with existing branches
- Diagnoses failing PR titles and returns a fixed title that passes
- Gives a confirm-first command sequence: clean tree check, fetch, branch from the fresh base, push, then
gh pr create --draftwith an explicit title
What you get
A copyable branch name and PR title with a one-line reason for the type and scope. If you ask for setup, you also get the exact commands to create the branch and open the draft PR. Batches come back as a table.
Best for
Developers and teams on GitHub or GitLab who use Conventional Commits, squash merges, semantic-release, or Jira/Linear ticket linking and want every branch and PR title to pass CI on the first try.
SKILL.md preview
---
name: git-branch-names-conventional-pr-titles
description: Turns a feature, bug, or ticket description into a branch name and PR title that match the repo's existing convention (Conventional Commits type, scope, ticket key). It checks both against git ref rules, commitlint-style title rules, and tracker-linking behavior, then gives confirm-first commands to create the branch and open a draft PR. Use when the user says "name this branch", "what should I call this PR", "give me a conventional commit title for this", "start a branch for PROJ-482", "create the branch and open a draft PR", "my PR titles keep failing the commitlint check", "Jira isn't linking my branch".
---
… (sign up to view the full skill)More development skills
View all Development skills →Performance Bottleneck Profiling: Node, Python, Go
Classifies a slowdown, gives exact profiler commands, reads the output, and proves the fix with same-conditions p95/p99 numbers.
Feature Scaffolding with Working Tests
Turn a short feature spec into code, runnable tests, and integration wiring that match your existing project.
Feature Flag Rollouts and Kill Switches
Design staged flag rollouts, verify rollback paths, and audit flag debt with explicit defaults, gates, and retirement plans.
Microcontroller Firmware and RTOS Engineering
Build and debug MCU firmware with bounded ISR/RTOS timing, safe DMA ownership, and measured power budgets.