git-workflow-and-versioning

Structures git commits, branching, and semantic versioning into disciplined workflows.

Updated Sep 8, 2026
One-click install
npx skills add https://github.com/sasidhar4444/ai-receptionist --skill git-workflow-and-versioning-sasidhar4444
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow-and-versioning
Source: https://github.com/sasidhar4444/ai-receptionist/tree/main/agent-skills/skills/git-workflow-and-versioning
Command: npx skills add https://github.com/sasidhar4444/ai-receptionist --skill git-workflow-and-versioning-sasidhar4444

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents and developers generate code faster than they can organize it, leading to giant unreviewable commits, tangled branches, and releases with no clear version contract. This Skill enforces disciplined version control so every change stays reviewable, revertable, and traceable. ## Core Features & Use Cases - Atomic Commit Discipline: Enforces small, single-purpose commits with descriptive conventional messages (feat, fix, refactor, test, docs, chore) and pre-commit hygiene 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 multiple AI agents can work in parallel without conflicts. - Semantic Versioning & Releases: Defines MAJOR.MINOR.PATCH bump rules, annotated git tags as the source of truth, and human-readable changelogs grouped by Added/Changed/Fixed/Deprecated. - Use Case: An AI agent finishes a messy working session with mixed refactors and features; this Skill splits the work into clean atomic commits, writes proper messages, and prepares a tagged v1.4.0 release with a curated changelog entry. ## Quick Start Ask the agent to split the current uncommitted changes into atomic commits with conventional messages and prepare a semantic version 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 large uncommitted change into atomic commits?▼

Stage and commit one logical change at a time, keeping refactors separate from features and formatting separate from behavior changes. Target roughly 100 lines per commit, and split anything approaching 1000 lines into smaller self-contained changes.

What is the best git branching strategy for small teams?▼

Trunk-based development is the recommended default: keep main always deployable and merge short-lived feature branches within 1-3 days. Long-lived branches accumulate merge risk, so prefer feature flags over keeping incomplete work on a branch.

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

Use semantic versioning: major for breaking changes, minor for backward-compatible features, patch for backward-compatible fixes. When unsure whether a change is breaking, assume it is, since consumers may rely on behavior you consider internal.

Can multiple AI agents work on the same repo simultaneously?▼

Yes, use git worktrees to give each agent its own directory checked out to a separate branch. Agents work in parallel without branch switching, and failed experiments are removed by deleting the worktree.

Why should a changelog not be generated from git log?▼

Commit messages are written for developers, while a changelog is a curated consumer-facing summary grouped by impact such as Added, Fixed, and Deprecated. Dumping raw commits buries breaking changes and migration notes that users actually need.