git-workflow

Enforce local git discipline for clean commits and meaningful history.

3|1|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/deandum/claude-resources --skill git-workflow-deandum
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/deandum/claude-resources/tree/main/skills/core/git-workflow
Command: npx skills add https://github.com/deandum/claude-resources --skill git-workflow-deandum

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Local git discipline ensures that commits, branches, and PRs are understandable and traceable, reducing chaos in project history and reviews.

Core Features & Use Cases

  • Enforces one logical change per commit with clear, imperative messages.
  • Recommends consistent branch naming and structured PR descriptions to improve reviews.
  • Helps decide between rebase and merge strategies and documents versioning choices for local workflows.

Quick Start

Staging a change, write a clear, imperative commit message that explains why the change is needed.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I enforce one logical change per commit in my local git workflow?

To write clear commit messages, use imperative mood to explain why a change is needed rather than just what changed. This local git discipline ensures each commit represents one logical change, keeping project history understandable and traceable during reviews.

What's the best way to name git branches for consistent code reviews?

The best way to name git branches is to apply consistent branch naming conventions enforced by a local git workflow. This discipline improves code reviews by making branch intent clear and grouping related changes logically before submitting a PR.

How do I choose between rebase and merge strategies for a clean git history?

Choosing between rebase and merge strategies depends on your local git discipline goals for clean history. A structured workflow helps decide which approach best preserves meaningful commit sequence and reduces chaos in project history during reviews.

Should I use semver or calvert versioning for my local git workflow?

Choosing semver or calvert versioning for your local git workflow depends on your project's release cadence and versioning needs. A disciplined git workflow documents this choice to maintain consistent version tracking across local commits and branches.

How do I draft a structured PR description from local commits?

To draft a structured PR description from local commits, enforce one logical change per commit with clear messages. This local git discipline ensures your pull request descriptions accurately summarize meaningful history and improve the code review process.