git-conventions

Define conventional commit types and TDD-style commit rhythms for software projects.

3|1|Updated Mar 22, 2026

Search Tags:#git #workflow #tdd #commits #code-review #conventional-commits #version-history

Ready to run

npx skills add https://github.com/itzcull/software-skills --skill git-conventions-itzcull

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-conventions
Source: https://github.com/itzcull/software-skills/tree/main/skills/git-conventions
Command: npx skills add https://github.com/itzcull/software-skills --skill git-conventions-itzcull

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Git commit conventions ensure stable, reviewable project history by enforcing structured messages, consistent formatting, and safe change practices across a team.

Core Features & Use Cases

Stability-first commits: every change is documented with clear intent and passes tests and checks.
Conventional types: standardize messages with feat, fix, refactor, test, chore, and more.
TDD rhythm: promote committing after RED, GREEN, and REFACTOR steps to support reliable progress and rollback.
Practical workflows: guiding what to include in commit messages and how to review history for clarity.

Quick Start

Start by adopting conventional commits for your next change by labeling each commit with a clear type and descriptive subject.

Frequently Asked Questions about git-conventions

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

FAQPage Schema

What are conventional commits and how do they improve git history?▼

Conventional commits standardize git history by enforcing structured messages with specific type prefixes like feat, fix, and refactor. This practice ensures stable, reviewable project progression and clear intent across software development teams.

How do I structure commit messages for a clean version history?▼

Structure commit messages by applying conventional type prefixes such as feat, fix, chore, or test, followed by a descriptive subject. This enforces consistent formatting and safe change practices across the team's version history.

How does TDD commit rhythm work with conventional commits?▼

TDD commit rhythm promotes committing after RED, GREEN, and REFACTOR test phases. Combined with conventional commits, this practice supports reliable progress tracking and safe rollback points during software development.

Can I use git conventions for code review and PR standards?▼

Yes, git conventions define PR standards and guide what to include in commit messages for effective code review. This ensures every change is documented with clear intent and passes tests for reviewable history.

What is the best way to transition a team to conventional commit types?▼

The best way to transition is adopting conventional commits for the next change by labeling each commit with a clear type and descriptive subject, enforcing consistent formatting and structured messaging across the project.

When should I use specific conventional commit type prefixes?▼

Use conventional commit type prefixes like feat for new features, fix for bug patches, refactor for code restructuring, and chore for maintenance. This categorization enforces structured messages and readable project history.