Skip to content

Add Branch Convention community extension to catalog and README#2128

Merged
mnriem merged 1 commit intogithub:mainfrom
Quratulain-bilal:feat/branch-convention-extension
Apr 8, 2026
Merged

Add Branch Convention community extension to catalog and README#2128
mnriem merged 1 commit intogithub:mainfrom
Quratulain-bilal:feat/branch-convention-extension

Conversation

@Quratulain-bilal
Copy link
Copy Markdown
Contributor

Summary

  • Adds branch-convention entry to extensions/catalog.community.json (alphabetically between
    azure-devops and canon)
  • Adds Branch Convention row to README.md Community Extensions table (alphabetically between Azure DevOps Integration and Canon)

Extension Details

Field Value
ID branch-convention
Name Branch Convention
Commands 3 (configure, validate, rename)
Hooks 1 (before_specify)
Category process
Effect Read+Write
Requires spec-kit >= 0.4.0
Repository https://github.com/Quratulain-bilal/spec-kit-branch-convention

What 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 and
    confirmation

Template tokens: {seq}, {kebab}, {ticket}, {date}, {type}, {summary}

Checklist

  • Entry added to extensions/catalog.community.json in alphabetical order by ID
  • Row added to README.md Community Extensions table in alphabetical order by name
  • JSON validates successfully
  • Extension repo has valid extension.yml, all command files, README, CHANGELOG, and LICENSE
  • verified: false, downloads: 0, stars: 0 set for new submission
  • Only 2 files modified (catalog + README)

Closes #407

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>
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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-convention metadata entry to extensions/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 mnriem merged commit 3028a00 into github:main Apr 8, 2026
12 checks passed
@mnriem
Copy link
Copy Markdown
Collaborator

mnriem commented Apr 8, 2026

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature Request] Configurable naming convention for /specify branch and specs/ folder

3 participants