speckit-git-feature
Skill718 starsChanged 35 days agoApache-2.0View on GitHub
Create a feature branch with sequential or timestamp numbering
35 other projects use a version of this, 27 of them edited.
Adopted by
Most recently taken up by
- tohure/Diccionario-Muchikedited, first seen Nov 8, 2026
- zalando-incubator/agentic-identity-brokeredited, first seen Nov 8, 2026
- vizier-lab/vizieredited, first seen Nov 1, 2026
- superyaya44/claude-skillsedited, first seen Oct 20, 2026
- alfredoperez/speckit-companionedited, first seen Oct 19, 2026
- 2830500285/omni-agentedited, first seen Oct 13, 2026
Used with
Projects with it also use speckit-converge and commit.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Microsoft AzureSkillspeckit-converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
Also in 5 projects that use this
SentrySkillcommit
Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.
Also in 3 projects that use this
Other versions35 projects use a version of this.
Word for word · 8
- unoplatform/uno★ 10k100% same
- elsa-workflows/elsa-studio★ 302100% same
- PieroSierra/SecondBrain★ 152100% same
- HamedMP/matrix-os★ 86100% same
- ldilov/harness-forge★ 4100% same
- gyasis/chiron★ 2100% same
- abhibattula/Home-OS★ 0100% same
- Julian-Stancioff/agentforge★ 0100% same
Edited · 27
- pmndrs/react-spring★ 29k100% same
- elsa-workflows/elsa-core★ 7.9k100% same
- cloudposse/atmos★ 1.4k100% same
- opsmill/infrahub★ 54820% same
- sbaiahmed1/react-native-blur★ 350100% same
- haru/redmine_ai_helper★ 10796% same
- alfredoperez/speckit-companion★ 10462% same
- zalando-incubator/agentic-identity-broker★ 6886% same
- PIsberg/vibetags★ 25100% same
- vizier-lab/vizier★ 18100% same
17 more not listed
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- speckit-analyzeSkill
- speckit-checklistSkill
- speckit-clarifySkill
- speckit-constitutionSkill
- speckit-git-commitSkill
- speckit-git-initializeSkill
- speckit-git-remoteSkill
- speckit-git-validateSkill
- speckit-implementSkill
- speckit-planSkill
- speckit-specifySkill
- speckit-tasksSkill
- speckit-taskstoissuesSkill
The file
We split this skill into the rules it gives an agent
12 rules. 4 are common, 0 are distinctive, and 8 are very specific to this project.
4
Common
Most of the 27 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Create and switch to a new git feature branch for the given specification.
- Very specific: line 24
If the user explicitly provided GIT_BRANCH_NAME (e.g., via environment variable, argument, or in their request), pass it through to the …
- Very specific: line 31
Verify Git is available by running git rev-parse --is-inside-work-tree 2>/dev/null
- Common: line 32
If Git is not available, warn the user and skip branch creation
- Very specific: line 38
Check .specify/extensions/git/git-config.yml for branch_numbering value
- Very specific: line 39
Check .specify/init-options.json for branch_numbering value (backward compatibility)
- Very specific: line 40
Default to sequential if neither exists
- Common: line 46
Use action-noun format when possible (e.g., "add-user-auth", "fix-payment-bug")
- Common: line 49
Run the appropriate script based on your platform:
- Very specific: line 57
Do NOT pass --number — the script determines the correct next number automatically
- Very specific: line 58
Always include the JSON flag (--json for Bash, -Json for PowerShell) so the output can be parsed reliably
- Common: line 64
If Git is not installed or the current directory is not a Git repository:
“Common” is measured: kept by at least 6 in 10 of the 27 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Create Feature Branch
Create and switch to a new git feature branch for the given specification. This command handles branch creation only — the spec directory and files are created by the core /speckit.specify workflow.
User Input
$ARGUMENTSYou MUST consider the user input before proceeding (if not empty).
Environment Variable Override
If the user explicitly provided GIT_BRANCH_NAME (e.g., via environment variable, argument, or in their request), pass it through to the script by setting the GIT_BRANCH_NAME environment variable before invoking the script. When GIT_BRANCH_NAME is set:
- The script uses the exact value as the branch name, bypassing all prefix/suffix generation
--short-name,--number, and--timestampflags are ignoredFEATURE_NUMis extracted from the name if it starts with a numeric prefix, otherwise set to the full branch name
Prerequisites
- Verify Git is available by running
git rev-parse --is-inside-work-tree 2>/dev/null - If Git is not available, warn the user and skip branch creation
Branch Numbering Mode
Determine the branch numbering strategy by checking configuration in this order:
- Check
.specify/extensions/git/git-config.ymlforbranch_numberingvalue - Check
.specify/init-options.jsonforbranch_numberingvalue (backward compatibility) - Default to
sequentialif neither exists
Execution
Generate a concise short name (2-4 words) for the branch:
- Analyze the feature description and extract the most meaningful keywords
- Use action-noun format when possible (e.g., "add-user-auth", "fix-payment-bug")
- Preserve technical terms and acronyms (OAuth2, API, JWT, etc.)
Run the appropriate script based on your platform:
- Bash:
.specify/extensions/git/scripts/bash/create-new-feature.sh --json --short-name "<short-name>" "<feature description>" - Bash (timestamp):
.specify/extensions/git/scripts/bash/create-new-feature.sh --json --timestamp --short-name "<short-name>" "<feature description>" - PowerShell:
.specify/extensions/git/scripts/powershell/create-new-feature.ps1 -Json -ShortName "<short-name>" "<feature description>" - PowerShell (timestamp):
.specify/extensions/git/scripts/powershell/create-new-feature.ps1 -Json -Timestamp -ShortName "<short-name>" "<feature description>"
IMPORTANT:
- Do NOT pass
--number— the script determines the correct next number automatically - Always include the JSON flag (
--jsonfor Bash,-Jsonfor PowerShell) so the output can be parsed reliably - You must only ever run this script once per feature
- The JSON output will contain
BRANCH_NAMEandFEATURE_NUM
Graceful Degradation
If Git is not installed or the current directory is not a Git repository:
- Branch creation is skipped with a warning:
[specify] Warning: Git repository not detected; skipped branch creation - The script still outputs
BRANCH_NAMEandFEATURE_NUMso the caller can reference them
Output
The script outputs JSON with:
BRANCH_NAME: The branch name (e.g.,003-user-author20260319-143022-user-auth)FEATURE_NUM: The numeric or timestamp prefix used
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

