Add Branch Convention community extension to catalog and README#2128
Merged
mnriem merged 1 commit intogithub:mainfrom Apr 8, 2026
Merged
Conversation
Adds the spec-kit-branch-convention extension (3 commands, 1 hook) that enables configurable branch and folder naming with built-in presets for GitFlow, ticket-based, date-based, and custom patterns. Addresses community request in issue github#407 (39+ upvotes). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a new community extension (“Branch Convention”) to the project’s community extension discovery surfaces (the community catalog JSON and the README’s Community Extensions table), aligning with the request in issue #407 to make branch/folder naming configurable via an opt-in extension.
Changes:
- Added
branch-conventionmetadata entry toextensions/catalog.community.json(alphabetically by ID). - Added “Branch Convention” row to the README Community Extensions table (alphabetically by name).
Show a summary per file
| File | Description |
|---|---|
| README.md | Adds the “Branch Convention” entry to the Community Extensions table with category/effect and repo link. |
| extensions/catalog.community.json | Registers branch-convention in the community catalog with metadata (URLs, requirements, provides, tags, stats). |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 0
mnriem
approved these changes
Apr 8, 2026
Collaborator
|
Thank you! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
branch-conventionentry toextensions/catalog.community.json(alphabetically betweenazure-devopsandcanon)Branch Conventionrow to README.md Community Extensions table (alphabetically betweenAzure DevOps IntegrationandCanon)Extension Details
branch-conventionconfigure,validate,rename)before_specify)processWhat It Does
Configurable branch and folder naming conventions — addresses issue #407 (39+ upvotes), where the
maintainer explicitly said "We are going to separate Git branching and naming into an extension as an opt
in."
/speckit.branch-convention.configure— Set up naming rules with built-in presets (default, gitflow,ticket, date) or custom patterns
/speckit.branch-convention.validate— Check all branches and folders against the convention(read-only)
/speckit.branch-convention.rename— Safely rename non-compliant branches and folders with preview andconfirmation
Template tokens:
{seq},{kebab},{ticket},{date},{type},{summary}Checklist
extensions/catalog.community.jsonin alphabetical order by IDextension.yml, all command files, README, CHANGELOG, and LICENSEverified: false,downloads: 0,stars: 0set for new submissionCloses #407