skills.rest
ankaboot-source
ankaboot-sourceOFFICIAL
Explore all skills by this author →
WebsiteGitHub

git-workflow-and-versioning

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

2|Updated Jul 25, 2026
Search Tags:#git#changelog#version control#worktrees#branching#semantic versioning#commit conventions
One-click install
npx skills add https://github.com/ankaboot-source/boucle --skill git-workflow-and-versioning-ankaboot-source
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow-and-versioning
Source: https://github.com/ankaboot-source/boucle/tree/main/.jcode/skills/git-workflow-and-versioning
Command: npx skills add https://github.com/ankaboot-source/boucle --skill git-workflow-and-versioning-ankaboot-source

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents and developers generating code at high speed often produce giant unreviewable commits, vague messages, mixed concerns, 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 - Commit Discipline: Enforces atomic commits, conventional message types (feat, fix, refactor, test, docs, chore), and pre-commit hygiene checks for secrets, tests, and linting. - Branching & Parallel Work: Guides trunk-based development with short-lived feature branches and git worktrees for running parallel AI agent work safely. - 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 feature slice, runs tests, commits with a descriptive conventional message, and when cutting a release, tags v1.4.0 and writes a curated changelog entry with migration notes for breaking changes. ## Quick Start Use the git-workflow-and-versioning skill to commit my current changes as atomic conventional commits and prepare a tagged semver 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 write good git commit messages?▼

Use the format 'type: short description' with types like feat, fix, refactor, test, docs, or chore, followed by a body explaining why the change was made. Each commit should do one logical thing and stay around 100 lines for easy review and reversion.

How to run parallel AI agents on the same git repository?▼

Use git worktrees to create separate directories, each checked out to its own feature branch. Agents work in isolation without branch switching, and failed experiments are removed with 'git worktree remove' without losing other work.

What is trunk-based development vs gitflow?▼

Trunk-based development keeps main always deployable with short-lived feature branches merged within 1-3 days, while gitflow uses long-lived development branches. DORA research correlates trunk-based development with high-performing teams, though commit discipline matters more than the specific branching model.

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

Bump major for breaking changes requiring consumers to modify their code, 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 should a changelog not be generated from git log?▼

Commit logs are written for developers, while changelogs are curated for consumers answering 'what changed and do I care?'. Entries should be grouped by Added, Changed, Fixed, Deprecated, Removed, and Security, phrased around user impact, and written with the change itself rather than reconstructed at release time.

Related Skills

Explore More Software Engineering Skills→
nikegeorgian-stacknikegeorgian-stack

incremental-implementation

Implements multi-file code changes in tested, committed 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
narthurnarthur
6

split-pr

Split changes from a Git branch into a separate pull request.

Community
Advanced
jm96441njm96441n
40

jujutsu

Squash jj commits into clean history with stable change IDs.

Community
Advanced