git-conventions
/git-conventions
Git commit conventions covering stability invariants, conventional commit types (feat, fix, refactor, test, chore), message formatting (imperative voice, 50/72 rule), TDD commit rhythm (stable checkpoints after GREEN and REFACTOR), and PR standards. Use when writing commit messages, structuring commits, or reviewing git history quality.
- Author
- itzcull ↗
- Repository
- software-skills ↗
- Licence
- MIT
- Last repository change
- 04.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 04.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Git commit conventions covering stability invariants, conventional commit types (feat, fix, refactor, test, chore), message formatting (imperative voice, 50/72 rule), TDD commit rhythm (stable checkpoints after GREEN and REFACTOR), and PR standards. Use when writing commit messages, structuring commits, or reviewing git history quality.
Original author description
Git commit conventions covering stability invariants, conventional commit types (feat, fix, refactor, test, chore), message formatting (imperative voice, 50/72 rule), TDD commit rhythm (stable checkpoints after GREEN and REFACTOR), and PR standards. Use when writing commit messages, structuring commits, or reviewing git history quality.
How it works
- Purpose
- Relationship to structured development
- When to use
- Key principles
- Reference files
SKILL.md preview
--- name: git-conventions description: Git commit conventions covering stability invariants, conventional commit types (feat, fix, refactor, test, chore), message formatting (imperative voice, 50/72 rule), TDD commit rhythm (stable checkpoints after GREEN and REFACTOR), and PR standards. Use when writing commit messages, structuring commits, or reviewing git history quality. license: MIT metadata: author: itzcull --- ## Purpose Define the conventions for git commits that maintain a clean, bisectable, and meaningful project history. Every commit represents stable, working software with incremental, focused changes. ## Relationship to structured development Within [structured development](../structured-development/SKILL.md), this skill supplies [traceable change records](../structured-development/SKILL.md#conformance-requirements) and information for [review or continuation at scope handoff](../structured-development/SKILL.md#7-close-the-agreed-scope) across increments. Its commit boundaries preserve understandable history; they are not substitutes for the enclosing procedure's acceptance or release boundaries. Use the intended change, repository policy, available verification evidence, and the Git operation the user has authorized. Return proposed commit boundaries and messages, or the resulting commit or PR references when execution is requested, with an honest account of verification. Apply TDD-specific cadence when the procedure uses TDD rather than imposing test-first development on every procedure. A commit records a change; a PR presents it for review. Neither establishes acceptance or release readiness. If stability cannot be demonstrated, report the missing or failed checks instead of asserting a verified commit. This skill's conventions do not independently authorize committing, pushing, or merging. ## When to use - Writing commit messages - Deciding what to include in a single commit - Structuring commits during TDD (when to commit in RED-GREEN-REFACTOR) - Reviewing commit history quality - Setting up commit conventions for a new project - Understanding conventional commit types and their usage ## Key principles - **Stability first** - every commit must satisfy the repository's applicable stability checks; skipped required checks are not passes - **Incremental progress** - small, focused changes easy to review, revert, and bisect - **Imperative voice** - describe what the code DOES when applied - **Semantic clarity** - type prefixes indicate the nature of change at a glance - **TDD rhythm** - use stable checkpoints after GREEN and REFACTOR within the enclosing procedure's authorized commit boundaries ## Reference files - [Git commit conventions](references/git-commits.md) - Complete guide including stability invariants, commit types, message formatting, TDD commit rhythm, and PR standards
Files in this package (2)
- SKILL.md 3 KB
- references/git-commits.md 9 KB
Versions
The database has no other skills named git-conventions.
Database snapshot: 13.11.2026 · package version 60213d8ce952 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100conventional-commit
Write git commit messages following the Conventional Commits v1.0.0 specification. ALWAYS use this skill when committing code changes, writing commit messages, reviewing or validating commit message format — even when the user simply asks to "commit this" or "write a commit… - 100commit-message
Generate conventional commit messages - use when creating commits, writing commit messages, or asking for git commit help - 100plei-git
Write and review Git commit messages using Conventional Commits 1.0.0, or draft clear pull request descriptions for any project. Use when preparing commit messages or PR summaries; follow a repository's own conventions when they differ. - 95git-commits
Write clear, semantic git commit messages and PR/MR titles following Conventional Commits. Use when the user asks to write commit messages, format git history, improve commit quality, or set a PR/MR title, or mentions "commit message", "conventional commits", "merge message", or… - 90Conventional Commits
This skill should be used when the user asks to 'write commit message', 'create conventional commit', 'format git commit', 'follow commit conventions', 'structure commit message'. Provides Conventional Commits patterns for consistent, machine-readable commit messages. - 100commit
Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.