skills.rest
CodeCrafterAdi2006
CodeCrafterAdi2006COMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-workflow-and-versioning

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

Updated Jul 10, 2026
Search Tags:#git#changelog#version control#worktrees#branching#semantic versioning#commit conventions
One-click install
npx skills add https://github.com/CodeCrafterAdi2006/Ink-and-Code --skill git-workflow-and-versioning-codecrafteradi2006
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow-and-versioning
Source: https://github.com/CodeCrafterAdi2006/Ink-and-Code/tree/main/Skills/git-workflow-and-versioning
Command: npx skills add https://github.com/CodeCrafterAdi2006/Ink-and-Code --skill git-workflow-and-versioning-codecrafteradi2006

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-assisted coding produces changes at high speed, and without disciplined version control those 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 - Atomic Commit Discipline: Enforces small, single-purpose commits with conventional message types (feat, fix, refactor, test, docs, chore) and pre-commit checks for secrets, tests, and linting. - Trunk-Based Branching & Worktrees: Guides short-lived feature branches merged within 1-3 days, plus git worktree setups so parallel AI agents can work in isolated directories simultaneously. - Semantic Versioning & Changelogs: Defines MAJOR.MINOR.PATCH bump rules, annotated release 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 five commits, each tested and scoped; when cutting release v1.4.0, the version bump, annotated tag, and changelog entry are derived consistently so consumers know exactly what changed and whether upgrading is safe. ## Quick Start Ask the agent to commit the current changes following the git workflow skill, splitting them into atomic commits with conventional messages.

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' where type is feat, fix, refactor, test, docs, or chore. The message should explain why the change was made, not just what changed, with an optional body describing intent and context.

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

Trunk-based development keeps main always deployable with short-lived feature branches merged within 1-3 days. DORA research correlates it with high-performing teams, and it avoids the merge conflicts and integration delays of long-lived branches.

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

Bump MAJOR for breaking changes requiring consumer code updates, MINOR for backward-compatible new functionality, and PATCH for backward-compatible bug fixes. When unsure whether a change is breaking, assume it is, since consumers may rely on observed behavior.

Can multiple AI agents work on the same repo in parallel?▼

Yes, use git worktrees to give each agent its own directory checked out to a separate branch. Run 'git worktree add ../project-feature-a feature/name' so agents work in isolation without branch switching, then merge and remove worktrees when done.

What files should never be committed to git?▼

Never commit .env files with secrets, node_modules, build output like dist or .next, or credentials. Set up a .gitignore immediately covering these, and scan staged diffs for passwords, API keys, and tokens before every commit.

Why is a changelog different from git log output?▼

A changelog is curated for consumers, grouped by Added, Changed, Fixed, Deprecated, Removed, and Security, phrased around user impact. Raw commit logs bury what matters; write changelog entries with each change rather than reconstructing them at release time.

Related Skills

Explore More Software Engineering Skills→
mst-software-vnmst-software-vn
1

setup-pre-commit

Configures Husky pre-commit hooks with lint-staged, Prettier, typecheck, and tests.

Official
Intermediate
CHENyiru3CHENyiru3

managing-python-releases

Automate version bumps, changelog generation, and PyPI publishing for Python libraries.

Community
Advanced
DevelopersGlobalDevelopersGlobal
65

api-design

Design stable, versioned, self-documenting APIs using Hyrum's Law.

Official
Advanced
roanbrasilroanbrasil
5

git-workflow

Implement Git branching strategies, commit discipline, and PR practices.

Community
Advanced