Automated summary
Creates git branches following a type/short-description naming convention to organize work.
Strengths
- Clear and consistent naming for all team members
- Automatic categorization of work type (feat, fix, docs, etc.)
- Simplifies branch tracking and search
Limitations
- Does not cover all possible cases (e.g., release branches)
- No automatic validation without an additional hook
When starting a new task or feature to create a branch with a standardized name.
When the team already uses another established naming convention or a specific workflow (e.g., Git Flow).
Security analysis
SafeThe skill only instructs creating a git branch using standard naming conventions and git commands. No destructive, exfiltrating, or unsafe actions.
No concerns found
How this analysis is madeExamples
Create a branch for adding infinite scroll to the feedCreate a branch to fix the album path validation bugCreate a branch to add pre-commit hooks to the projectname: branch description: Creates git branches with proper naming. Use when creating branches, starting new work, or switching to feature branches.
Branch Naming
Use type/short-description format.
Types
feat: User-facing features or behavior changes (must change production code)fix: Bug fixes (must change production code)docs: Documentation onlystyle: Code style/formatting (no logic changes)refactor: Code restructuring without behavior changetest: Adding or updating testschore: CI/CD, tooling, dependency bumps, configs (no production code)
Examples
feat/infinite-scroll
fix/album-path-validation
refactor/state-management
chore/pre-commit-hooks
docs/update-readme
test/e2e-login-flow
Instructions
- Determine the type based on what the work will accomplish
- Choose a short, descriptive slug (2-4 words, hyphenated)
- Create the branch:
git checkout -b type/short-description
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/git-branch-naming-mm78nnz3/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/git-branch-naming-mm78nnz3' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/git-branch-naming-mm78nnz3/download' --output '.skill-downloads/git-branch-naming-mm78nnz3/SKILL.md.part' && mv '.skill-downloads/git-branch-naming-mm78nnz3/SKILL.md.part' '.skill-downloads/git-branch-naming-mm78nnz3/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/git-branch-naming-mm78nnz3/SKILL.md' && test -s '.skill-downloads/git-branch-naming-mm78nnz3/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/branch' && cp -R '.skill-downloads/git-branch-naming-mm78nnz3' '.claude/skills/branch'Cursor
test -f '.skill-downloads/git-branch-naming-mm78nnz3/SKILL.md' && test -s '.skill-downloads/git-branch-naming-mm78nnz3/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/branch' && cp -R '.skill-downloads/git-branch-naming-mm78nnz3' '.cursor/skills/branch'Codex
test -f '.skill-downloads/git-branch-naming-mm78nnz3/SKILL.md' && test -s '.skill-downloads/git-branch-naming-mm78nnz3/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/branch' && cp -R '.skill-downloads/git-branch-naming-mm78nnz3' '.agents/skills/branch'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/git-branch-naming-mm78nnz3'openskills read 'git-branch-naming-mm78nnz3'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/git-branch-naming-mm78nnz3/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.