SprintKit
Back to Dev Tools
100% Client-side & Private Sandbox

Git Branch & Semantic Commit Builder

Git & Workflow

Generate Conventional Commits specification messages and standardized Jira branch names.

Formatted Git Commit MessageCONVENTIONAL
Plain Text / Monospace5 lines · 141 chars
Guide & Documentation

Conventional Commits & Standardized Git Branch Name Generator

Build clean, standardized Git commit messages compliant with the Conventional Commits specification. Generate consistent feature, bugfix, and hotfix branch names paired with Jira ticket keys.

How to Build Conventional Git Commits

01

Select Commit Type & Scope

Choose semantic type (feat, fix, refactor, chore, docs, test) and specify module scope (e.g. 'auth', 'cart').

02

Add Jira Key & Description

Input your ticket identifier and imperative mood summary; optionally flag breaking changes with '!' markers.

03

Copy Formatted Git Commands

Copy ready-to-run 'git checkout -b ...' branch commands or 'git commit -m ...' terminal strings.

Git Helper Capabilities

Conventional Commits 1.0.0 Compliance

Enforces standard syntax required by semantic-release, automated changelog generators, and CI linters.

Breaking Change Flagging

Automatically injects the '!' breaking change marker and 'BREAKING CHANGE:' footer notes.

Standardized Branch Naming

Generates clean kebab-cased branch names like 'feature/PROJ-102-retry-payment' following team conventions.

Git Workflow Best Practices

  • §1Write commit messages in the imperative present tense ('add feature' rather than 'added feature').
  • §2Keep the first line (header) under 72 characters so it displays cleanly in terminal logs and GitHub UI.
  • §3Use semantic types consistently so automated release tooling can calculate correct semver version bumps.

Frequently Asked Questions

What is the Conventional Commits specification?
Conventional Commits is a lightweight convention on top of commit messages that provides an explicit commit history, making it easy to automate semantic versioning and changelogs.
What are the common commit types?
feat: new feature; fix: bug fix; refactor: code change that neither fixes a bug nor adds a feature; chore: build tasks or package bumps; docs: documentation only.
Does this tool integrate with my terminal?
Yes, clicking copy provides the full command line string (e.g. `git commit -m "..."`) ready to paste into your shell.

Related Agile & Developer Tools

PR Review Queue

Track pull requests created from your git branches.

Development Checklist

Pre-commit checklist for local tests and security audits.

Case & Slug Converter

Format branch slugs and ticket identifiers.