git-hygiene

Enforce atomic git commits with task references and clean repositories.

Updated Jan 23, 2026

Search Tags:#git #workflow #version control #pre-commit #commit hygiene #task linking

Ready to run

npx skills add https://github.com/datorresb/vibecoding-starter --skill git-hygiene-datorresb

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-hygiene
Source: https://github.com/datorresb/vibecoding-starter/tree/main/.claude/skills/core/git-hygiene
Command: npx skills add https://github.com/datorresb/vibecoding-starter --skill git-hygiene-datorresb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces git commit hygiene, ensuring every task ends with an atomic, traceable commit and keeps the repository clean between sessions.

Core Features & Use Cases

Atomic commits per task: Each task results in a single, reviewable commit that references the task ID.
Task-to-commit linking: Commits include explicit task references and can be surfaced in task trackers.
Pre-commit and hygiene rules: Guidance for code review, branching, and pushing to maintain clean history.

Quick Start

Apply the git-hygiene guidelines to your current project by starting a new task, then commit changes with a structured message referencing the task ID, update the task notes with the commit hash, and keep the working tree clean before moving to the next task.

Frequently Asked Questions about git-hygiene

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

FAQPage Schema

How do I enforce task linking in git commits?▼

Enforce task linking in git commits by applying structured commit messages that explicitly reference the task ID. This ensures every commit remains traceable and can be surfaced directly in task trackers.

What are atomic commits per task in version control?▼

Atomic commits per task ensure each task results in a single, reviewable commit. This approach keeps the repository clean between sessions and maintains a clear history for code review and branching.

How do I structure pre-commit checks for a clean git workflow?▼

Structure pre-commit checks for a clean git workflow by following hygiene rules that guide code review, branching, and pushing. This keeps the working tree clean before moving to the next task.

Do I need to update task notes with commit hashes?▼

Yes, you need to update task notes with commit hashes to ensure traceable task commits. This step links the task tracker to the exact version control state after changes are applied.

What is the best way to keep the working tree clean between sessions?▼

The best way to keep the working tree clean between sessions is to enforce atomic commits per task and follow pre-commit hygiene rules. This prevents leftover changes from affecting new branches.