core-git

Enforces atomic commits, branch workflows, and commit formatting for Git operations.

1|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/justin-delano/Claude-Config --skill core-git
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: core-git
Source: https://github.com/justin-delano/Claude-Config/tree/main/skills/core/git
Command: npx skills add https://github.com/justin-delano/Claude-Config --skill core-git

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git teams often struggle with inconsistent commit history and unclear branch practices, slowing reviews and releases.

Core Features & Use Cases

  • Atomic commits after each file edit to create small, reviewable changes.
  • Strict branch workflow guidance including naming and merge practices for feature, bugfix, and release branches.
  • Consistent commit messages and formatting rules to improve readability and traceability.
  • Use Case: When starting a new feature, apply deterministic commits and a defined branch strategy to streamline code reviews and releases.

Quick Start

Ask the assistant to apply atomic commits and a standard branch workflow during your next git operation.

Frequently Asked Questions about core-git

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

FAQPage Schema
How do I enforce atomic commits in git after every file edit?

You can enforce atomic commits in git by applying strict version control conventions that require immediate, small, reviewable changes after each file edit. This Skill automates that workflow to ensure your commit history stays clean and traceable.

What is the best way to standardize git branch naming for feature and release workflows?

Standardizing git branch naming involves applying explicit branch workflow guidance for feature, bugfix, and release branches. This Skill enforces strict naming conventions and controlled merge practices to streamline code reviews and release preparation.

How do I format git commit messages to improve traceability across team projects?

Formatting git commit messages for traceability requires applying consistent commit message rules and formatting standards. This Skill enforces deterministic commit formatting to improve readability and make code changes easier to track during reviews.

Does this git commit workflow support jujutsu or beads as an alternative to standard version control?

Yes, this git commit workflow supports jujutsu (jj) and beads workflows. It provides optional guidance for these version control systems alongside its core strict rules for atomic commits and branch workflows.

Why should I use atomic commits instead of batching changes in a single git commit?

Atomic commits create small, reviewable changes that simplify code reviews and release preparation. Batching changes in a single git commit obscures traceability and slows down team reviews, which this Skill prevents by enforcing immediate commits after edits.

Can I apply this git history cleanup convention to an existing repository with mixed commit practices?

Yes, you can apply this git history cleanup convention to an existing repository. The Skill provides controlled history hygiene rules and commit formatting standards that can be applied to ongoing software development workflows to improve consistency.