skills.rest
maestria-co
maestria-coOFFICIAL
Explore all skills by this author →
GitHub

commit-discipline

Standardize commit messages and branch naming with Conventional Commits.

Updated Mar 2, 2026
Search Tags:#git#workflow#commit#branching#atomic-commits#version-control#conventional-commits
One-click install
npx skills add https://github.com/maestria-co/ai-playbook --skill commit-discipline-maestria-co
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-discipline
Source: https://github.com/maestria-co/ai-playbook/tree/main/skills/commit-discipline
Command: npx skills add https://github.com/maestria-co/ai-playbook --skill commit-discipline-maestria-co

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual git workflows often produce messy histories that hinder review, debugging, and collaboration. This skill defines a standard for commit messages, branch naming, atomic changes, and what should (and shouldn't) be committed to keep history readable and trustworthy.

Core Features & Use Cases

  • Enforces Conventional Commits for consistent message formatting
  • Defines atomic commits and scope usage to keep changes small and reviewable
  • Provides branch-naming guidelines to avoid conflicts and improve navigation
  • Includes checks for what not to commit (credentials, binaries, secrets) to minimize leakage
  • Helps teams align on project conventions and streamline review processes

Quick Start

Adopt the prescribed commit discipline in your workflow to ensure consistent, machine-readable history.

Frequently Asked Questions about commit-discipline

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

FAQPage Schema
How do I enforce Conventional Commits and atomic commits in my git workflow?▼

To enforce Conventional Commits and atomic commits in your git workflow, standardize commit messages and scope usage to keep changes small, reviewable, and traceable across software projects of any size.

What is the best way to prevent secrets and credentials from entering my git history?▼

The best way to prevent secrets and credentials from entering your git history is to apply commit discipline checks that identify what not to commit, safeguarding your repository against accidental leakage of sensitive data.

How do I name git branches to improve traceability and avoid conflicts in version control?▼

To improve traceability and avoid conflicts in version control, apply branch-naming guidelines that align with project conventions, ensuring repository navigation and history remain clean and meaningful.

When do I need atomic commits in version control, and what problem do they solve?▼

You need atomic commits in version control when manual git workflows produce messy histories that hinder debugging and collaboration. They define small, focused changes to keep your repository history readable and reviewable.

Can I use commit discipline standards for software projects of any size?▼

Yes, you can use commit discipline standards for software projects of any size. They define commit messages, branch naming, and project-convention alignment to streamline review processes and safeguard repositories universally.

Related Skills

Explore More Software Engineering Skills→
semirm-devsemirm-dev

git-conventions

Validate Git branch names and commit messages against project conventions.

Community
Intermediate
zhangzhang-111-izhangzhang-111-i
2

changelog-generator

Generate changelog entries from Conventional Commits in markdown or JSON.

Community
Intermediate
fsx950223fsx950223
2

Commit and Push Staged Changes

Commit staged Git changes and push to the current branch with rebase conflict resolution.

Community
Intermediate
vulikjulikvulikjulik

aif-commit

Generate conventional commit messages from staged git changes.

Community
Intermediate