git-workflow-and-versioning

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

Updated May 13, 2026
One-click install
npx skills add https://github.com/sapatamuku-creator/mastersapatamuku --skill git-workflow-and-versioning-sapatamuku-creator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow-and-versioning
Source: https://github.com/sapatamuku-creator/mastersapatamuku/tree/main/releases/v2.7/.agents/skills/git-workflow-and-versioning
Command: npx skills add https://github.com/sapatamuku-creator/mastersapatamuku --skill git-workflow-and-versioning-sapatamuku-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents and developers generate code quickly, but without disciplined version control, changes become unreviewable, hard to revert, and risky to release. This Skill enforces atomic commits, short-lived branches, semantic versioning, and curated changelogs so every change stays manageable and every release communicates clearly to consumers. ## Core Features & Use Cases - Commit Discipline: Enforces atomic commits with conventional message types (feat, fix, refactor, test, docs, chore), pre-commit hygiene checks, and change summaries that document scope. - Branching & Parallel Work: Guides trunk-based development with short-lived feature branches, branch naming conventions, and git worktrees for running multiple AI agents in parallel. - Release & Versioning: Applies semantic versioning rules (MAJOR.MINOR.PATCH), annotated git tags as the source of truth, and human-readable changelogs grouped by Added/Changed/Fixed/Deprecated. - Use Case: An AI agent completes a feature across several commits, you tag v1.4.0, derive the version from the tag, and publish a changelog entry written alongside the change rather than reconstructed at release time. ## Quick Start Ask the agent to commit the current changes as atomic commits with conventional messages, then tag the release and write a changelog entry for the new version.

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. The body should explain why the change was made, not what changed, since the diff already shows that. Each commit should do one logical thing.

How do I choose a semantic version bump for a release?▼

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.

How do I run multiple AI agents on the same repo in parallel?▼

Use git worktrees to give each agent its own directory checked out to a separate branch, for example 'git worktree add ../project-feature-a feature/task-creation'. Agents work in isolation without branch switching, and failed experiments are removed with 'git worktree remove'.

What is the difference between a changelog and git log?▼

A changelog is a curated, consumer-facing summary grouped by Added, Changed, Fixed, Deprecated, Removed, and Security, phrased around user impact. Git log is a raw commit history written for developers, so dumping it as a changelog buries what matters.

When should I use long-lived branches instead of trunk-based development?▼

Long-lived development branches are discouraged because they accumulate merge risk daily. Release branches are acceptable for stabilizing a release while main moves forward, and feature flags are preferred over long branches for incomplete work.