skills.rest
MSC72m
MSC72mCOMMUNITY
Explore all skills by this author →
𝕏@MSC72mGitHub

git-workflow-and-versioning

Structures git commits, branching, worktrees, and semantic versioning releases.

Updated Aug 22, 2026
Search Tags:#git#changelog#version control#worktrees#branching#semantic versioning#atomic commits
One-click install
npx skills add https://github.com/MSC72m/DevForge --skill git-workflow-and-versioning-msc72m
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow-and-versioning
Source: https://github.com/MSC72m/DevForge/tree/main/skills/git-workflow-and-versioning
Command: npx skills add https://github.com/MSC72m/DevForge --skill git-workflow-and-versioning-msc72m

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents generate code at high speed, and without disciplined version control, changes become unreviewable, hard to revert, and impossible to release safely. This Skill enforces atomic commits, clean branching, and a proper versioning contract so every change stays manageable and every release is reproducible. ## Core Features & Use Cases - Atomic Commit Discipline: Enforces commit-early-commit-often workflows with conventional message types (feat, fix, refactor, test, docs, chore) and pre-commit hygiene checks for secrets, tests, and linting. - Branching & Worktrees: Guides trunk-based development with short-lived feature branches and git worktrees so multiple agents can work in parallel without interfering. - 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 messy working session with mixed changes. Use this Skill to split the work into clean atomic commits, write descriptive messages, then tag v1.4.0 and draft the changelog entry. ## Quick Start Use the git-workflow-and-versioning skill to split my uncommitted changes into atomic commits and prepare a tagged release with a changelog entry.

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 split a messy working tree into atomic commits?▼

Stage and commit one logical change at a time, keeping each commit self-contained around a single concern. Separate refactoring from feature work, and never mix formatting changes with behavior changes in the same commit.

What is the conventional commit message format?▼

Use a type prefix followed by a short description, such as "feat: add email validation to registration endpoint". Valid types are feat, fix, refactor, test, docs, and chore, with an optional body explaining why the change was made.

How do git worktrees help parallel AI agent work?▼

Git worktrees let you check out multiple branches into separate directories simultaneously with "git worktree add". Each agent works in its own directory and branch, so experiments stay isolated and failed work is removed without affecting main.

When should I bump major, minor, or patch versions?▼

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 is a changelog different from git log output?▼

A changelog is a curated, consumer-facing summary grouped by Added, Changed, Fixed, Deprecated, Removed, and Security, phrased around user impact. Raw commit logs bury what matters and are written for developers, not consumers.

What files should never be committed to git?▼

Never commit build output like dist/ or .next/, environment files like .env, or dependency folders like node_modules/. Set up a .gitignore immediately and check staged diffs for passwords, secrets, API keys, and tokens before committing.

Related Skills

Explore More Software Engineering Skills→
addyosmaniaddyosmani
84.9k

incremental-implementation

Implement software changes in small, testable vertical slices.

Community
Intermediate
BlockRunAIBlockRunAI
6.6k

release

Executes the full ClawRouter release checklist from version bump through npm publish and GitHub release.

Official
Intermediate
limaonlimaon

requesting-code-review

Evaluate code changes for quality and compliance before merging.

Community
Basic
metalagmanmetalagman
21

gitflow

Enforce Gitflow branching conventions and PR targets across develop and master branches.

Community
Advanced