skills.rest
Kunj-Sharma03
Kunj-Sharma03COMMUNITY
Explore all skills by this author →
GitHub

git-workflow-and-versioning

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

Updated Aug 11, 2026
Search Tags:#git#changelog#version control#worktrees#commit messages#branching#semantic versioning
One-click install
npx skills add https://github.com/Kunj-Sharma03/agent-contextify --skill git-workflow-and-versioning-kunj-sharma03
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow-and-versioning
Source: https://github.com/Kunj-Sharma03/agent-contextify/tree/main/templates/skills/git-workflow-and-versioning
Command: npx skills add https://github.com/Kunj-Sharma03/agent-contextify --skill git-workflow-and-versioning-kunj-sharma03

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 risky to release. This Skill enforces atomic commits, short-lived branches, semantic versioning, and curated changelogs so every change stays manageable and traceable. ## Core Features & Use Cases - Commit Discipline: Enforces atomic commits with conventional message types (feat, fix, refactor, test, docs, chore) that explain the why behind each change. - Branching & Worktrees: Guides trunk-based development with short-lived feature branches and git worktrees for parallel AI agent work. - 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 completes a feature across several commits, then you ask it to cut a release — it determines the correct version bump, tags v1.4.0, and writes a changelog entry grouped by Added/Fixed/Deprecated. ## Quick Start Use the git-workflow-and-versioning skill to review my uncommitted changes, split them into atomic commits with proper messages, and prepare a semver release tag 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 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. Each commit should do one logical thing, and the message should explain intent rather than restate the diff.

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

Trunk-based development keeps main always deployable, with work done in 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 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.

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

Use git worktrees to give each agent its own directory checked out to a separate branch, such as 'git worktree add ../project-feature-a feature/task-creation'. Agents work in isolation without branch switching, and worktrees are removed after merging.

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 covering these immediately, and check staged diffs for secrets like passwords, API keys, and tokens before every commit.

Is a changelog the same as a git commit log?▼

No. A changelog is a curated, consumer-facing summary grouped by Added, Changed, Fixed, Deprecated, Removed, and Security, phrased around user impact. Write each entry in the same change that introduces it rather than reconstructing it from commit history at release time.

Related Skills

Explore More Software Engineering Skills→
AmbroseTriCAmbroseTriC

commit

Stage, commit, and merge git changes with pull requests.

Community
Basic
mifunedevmifunedev
28

release

Automate CalVer release workflows with version computation, pre-flight checks, and artifact publishing.

Official
Advanced
authrain-cloud-abdullahformuliauthrain-cloud-abdullahformuli

code-review-and-quality

Reviews code changes across correctness, readability, architecture, security, and performance before merge.

Community
Intermediate
cr330326cr330326

git-workflow

Enforce a gitflow-like branching model with conventional commit standards.

Community
Advanced