git-workflow-and-versioning

Structures git commits, branching, semantic versioning, and changelog practices for code changes.

2|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/MoofonLi/dev-ready --skill git-workflow-and-versioning-moofonli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow-and-versioning
Source: https://github.com/MoofonLi/dev-ready/tree/main/src/dev_ready/templates/claude/skills/git-workflow-and-versioning
Command: npx skills add https://github.com/MoofonLi/dev-ready --skill git-workflow-and-versioning-moofonli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents generate code at high speed, and without disciplined version control, changes become unreviewable, irreversible, and untraceable. This Skill enforces commit hygiene, branching discipline, and release versioning so every change stays manageable and every release carries a clear contract for consumers. ## Core Features & Use Cases - Commit Discipline: Enforces atomic commits, descriptive conventional messages (feat/fix/refactor/test/docs/chore), separation of concerns, and pre-commit hygiene checks for secrets, tests, and linting. - Branching & Parallel Work: Guides trunk-based development with short-lived feature branches, branch naming conventions, and git worktrees so multiple agents can work in parallel without interference. - Release & Versioning: Applies semantic versioning (MAJOR.MINOR.PATCH), annotated git tags as the source of truth, and human-readable changelogs grouped by impact. - Use Case: An agent finishes a feature slice, runs tests, commits with a descriptive message, and when cutting a release, tags v1.4.0 and writes a curated changelog entry instead of dumping raw commit logs. ## Quick Start Ask the agent to commit the current changes as atomic commits with conventional messages and verify no secrets are staged before committing.

Frequently Asked Questions about git-workflow-and-versioning

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

FAQPage Schema
How do I write good git commit messages?

Use the format 'type: short description' with types like feat, fix, refactor, test, docs, or chore, followed by an optional body explaining why the change was made. The message should explain intent, not just restate what the diff shows.

What is trunk-based development and when should I use it?

Trunk-based development keeps main always deployable with short-lived feature branches merged within 1-3 days. It is the recommended default because long-lived branches accumulate merge risk, and DORA research links it to high-performing engineering teams.

How do I run multiple AI agents on parallel git branches?

Use git worktrees to create separate directories, each checked out to its own branch, so agents work in parallel without branch switching or interference. Remove the worktree after merging to clean up.

How do I choose between major, minor, and patch version bumps?

Bump MAJOR for breaking changes, MINOR for backward-compatible new functionality, and PATCH for backward-compatible bug fixes. When unsure whether a change is breaking, assume it is, since a surprise major is cheaper than a broken consumer.

Why should a changelog not just be the git commit log?

Commits are written for developers, while a changelog is curated for consumers and grouped by impact (Added, Changed, Fixed, Deprecated, Removed, Security). Dumping raw commits buries what matters, so write each entry with the change while the impact is fresh.