git-conventions

Apply standardized Git branch naming and commit message conventions.

Updated Dec 23, 2025

Search Tags:#git #workflow #branching #conventions #version-control #commit-message #conventional-commits

Ready to run

npx skills add https://github.com/BNTang/Sa-Token-Demo --skill git-conventions-bntang

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-conventions
Source: https://github.com/BNTang/Sa-Token-Demo/tree/main/.claude/skills/git-conventions
Command: npx skills add https://github.com/BNTang/Sa-Token-Demo --skill git-conventions-bntang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a clear, standardized set of Git conventions to ensure consistent branch naming, commit message formats, and development workflows across teams.

Core Features & Use Cases

Branch naming conventions for main/master, develop, feature/, fix/, hotfix/, release/, docs/, and refactor/.
Commit message formats based on Conventional Commits to improve history readability.
Branch lifecycle guidance from creation to merge and cleanup, including typical workflows like Git Flow, GitHub Flow, and trunk-based development.
Real-world use case: align a new feature branch with a predictable commit history and release process.

Quick Start

Use this Skill to establish and apply Git conventions across new and existing repositories. For example, enforce a feature branch naming pattern and standard commit messages.

Frequently Asked Questions about git-conventions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is the best way to standardize Git branch naming conventions across a team?▼

Standardizing Git branch naming conventions involves defining specific prefixes like feature/*, fix/*, and hotfix/* for different tasks. This ensures consistent branch lifecycles and integrates seamlessly with established workflows like Git Flow or GitHub Flow.

How do I format Git commit messages to improve project history readability?▼

Format Git commit messages using the Conventional Commits structure to significantly improve history readability. This standardized approach encodes clear rules for commit structure, allowing AI assistants to automatically apply and enforce consistent message formatting.

Does this support both Git Flow and trunk-based development workflows?▼

Yes, it supports common Git workflows including Git Flow, GitHub Flow, and trunk-based development. It provides concrete rules for branch lifecycles, managing releases, and aligning feature branches with predictable commit histories.

How do I manage branch lifecycles from creation to merge using standard conventions?▼

Manage branch lifecycles using standardized conventions for main, develop, and feature branches, tracking them from creation through merge and cleanup. This ensures predictable release processes and maintains a clean, unified project history.

When do I need Conventional Commits for my version control workflow?▼

You need Conventional Commits when standardizing version control workflows to ensure consistent commit message formats and predictable release processes. This approach encodes concrete rules that an AI assistant can apply in real-time to maintain history readability.