git-hygiene

Standardize Git commit messages, branching, and history rewrites.

5|1|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/wolf5996/agentic-skills --skill git-hygiene-wolf5996
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-hygiene
Source: https://github.com/wolf5996/agentic-skills/tree/main/git-hygiene
Command: npx skills add https://github.com/wolf5996/agentic-skills --skill git-hygiene-wolf5996

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git history becomes hard to review, revert, and maintain when commit messages are inconsistent, changes are bundled together, or commit/branch workflows are unclear.

Core Features & Use Cases

  • Conventional Commits compliance: Enforces type/scope formatting, lowercase subjects, and an imperative mood to make history readable and automatable.
  • Atomic commit discipline: Promotes one logical change per commit and provides guidance for splitting bundled changes.
  • Branching and history rewrite rules: Covers branch naming, merge conventions, and when to use rebase/squash with a focus on clean outcomes.
  • Practical .gitignore guidance: Recommends a whitelisting approach and enumerates common generated/intermediate files to exclude.

Quick Start

Ask an AI agent to “prepare a commit for my changes using Conventional Commits (with an optional scope), keep it atomic, and suggest the correct .gitignore entries for any generated files.”

Frequently Asked Questions about git-hygiene

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

FAQPage Schema
How do I write conventional commit messages in git?

Conventional commit messages enforce type/scope formatting, lowercase subjects, and imperative mood to keep git history readable and automatable. This standardization makes repository history clear, reviewable, and maintainable across development teams.

What is the best way to split bundled git commits into atomic changes?

Atomic commit discipline promotes one logical change per git commit and provides guidance for splitting bundled changes. This practice keeps version control history clean, simplifies reverting specific features, and ensures changes are easily reviewable.

When should I use git rebase or squash to clean up history?

Git rebase or squash should be used during history rewrite scenarios when you need clean outcomes for bundled commits. This history cleanup approach focuses on standardizing branch management, merge conventions, and maintaining a clear version control history.

How do I configure .gitignore to exclude generated and intermediate files?

Configuring .gitignore recommends a whitelisting approach and enumerates common generated or intermediate files to exclude. This prevents unwanted files from cluttering your repository while ensuring necessary tracked files remain in version control history.

Does this git branching approach require pre-commit verification checks?

Yes, git branching and commit standardization requires pre-commit verification checks to ensure commit message style and atomic one-change-per-commit discipline are followed before changes are finalized in repository history.