skills.rest
All-The-Vibes
All-The-VibesOFFICIAL
Explore all skills by this author →
GitHub

git-hygiene

Enforce atomic git commits linked to tasks with pre-commit checks.

4|2|Updated Jan 10, 2026
Search Tags:#git#commit#code-review#atomic-commits#version-control#task-tracking
One-click install
npx skills add https://github.com/All-The-Vibes/skills-catalog --skill git-hygiene-all-the-vibes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-hygiene
Source: https://github.com/All-The-Vibes/skills-catalog/tree/main/.claude/skills/core/git-hygiene
Command: npx skills add https://github.com/All-The-Vibes/skills-catalog --skill git-hygiene-all-the-vibes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures that every change is committed in a clean, atomic unit and that commits are linked to the corresponding task, preventing stray work and orphaned changes.

Core Features & Use Cases

  • Atomic commits: One commit per task to maximize traceability and reviewability.
  • Task linking: Commits reference a task ID and automatically update the task with the commit hash.
  • Pre-commit hygiene: Enforces checks before commit (no secrets, proper branch naming, and keeping a clean working tree).
  • Use Case: When finishing a task, you commit with a task reference like [task-42] Add feature, ensuring complete traceability.

Quick Start

Instruct the agent to enforce atomic commits, link commits to tasks, and keep the repository clean after every session.

Frequently Asked Questions about git-hygiene

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

FAQPage Schema
How do I keep my git commits clean and atomic for better code review?▼

Atomic commits involve creating one commit per task and linking it to a task ID. This practice maximizes traceability and reviewability by ensuring every change is a clean, atomic unit, preventing stray work and orphaned changes.

How do I link a git commit to a task tracking ID?▼

Link a git commit to a task tracking ID by including the task reference directly in the commit message, such as [task-42] Add feature. The system then automatically updates the corresponding task with the commit hash for complete traceability.

What pre-commit checks should I use for git version control hygiene?▼

Essential pre-commit checks for git version control hygiene include scanning for secrets, enforcing proper branch naming, and ensuring a clean working tree. These checks prevent sensitive data leaks and maintain a safe repository state before committing changes.

Can I use atomic commits and task linking across multi-repository workflows?▼

Yes, atomic commits and task linking are applicable across multi-repository workflows for feature development, bug fixes, and refactoring. This ensures a traceable history and safe rollback capabilities across all your repositories.

Why does leaving uncommitted changes in a working tree cause problems?▼

Leaving uncommitted changes causes problems by creating orphaned changes that break traceability and complicate code review. Enforcing a clean working tree after every session prevents stray work and ensures safe rollback.

Related Skills

Explore More Software Engineering Skills→
iltan987iltan987

speckit-git-initialize

Initialize a Git repository with an initial commit in a project directory.

Community
Intermediate
vankichivankichi

commit-push-branch

Create branches, commit changes, and push to a Git remote repository.

Community
Intermediate
kang8kang8
2

commit

Create git commits from staged changes with branch naming and validation.

Community
Advanced
vulikjulikvulikjulik

aif-commit

Generate conventional commit messages from staged git changes.

Community
Intermediate