git-workflow-and-versioning SKILL.md skillA

git-workflow-and-versioning from jpeetz/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

mdr add jpeetz/agent-skills/git-workflow-and-versioning@git:20261028.e711966

Pins git:20261028.e711966 in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

jpeetz/agent-skills

Path

skills/git-release/git-workflow-and-versioning/SKILL.md

Versions recorded

2

Latest version

git:20261028.e711966, committed Oct 28, 2026

First version recorded

Oct 5, 2026

Size

11,483 bytes

Repository stars

16

License

none declared

Use this skill when making any code change — committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or organizing work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump, tagging, or writing a changelog.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Git Workflow and Versioning

## Overview

Git is your safety net. Treat commits as save points, branches as sandboxes, and history as documentation. With AI agents generating code at high speed, disciplined version control is the mechanism that keeps changes manageable, reviewable, and reversible.

## When to Use

Always. Every code change flows through git.

## Core Principles

### Trunk-Based Development (Recommended)

Keep `main` always deployable. Work in short-lived feature branches that merge back within 1-3 days. Long-lived development branches are hidden costs — they diverge, create merge conflicts, and delay integration. DORA research consistently shows trunk-based development correlates with high-performing engineering teams.

```
main ──●──●──●──●──●──●──●──●──●──  (always deployable)
        ╲      ╱  ╲    ╱
         ●──●─╱    ●──╱    ← short-lived feature branches (1-3 days)
```

- **Dev branches are costs.** Every day a branch lives, it accumulates merge risk.
- **Release branches are acceptable.** When you need to stabilize a release while main moves forward.
…

Read the whole file at its exact version.

How to install

mdr add jpeetz/agent-skills/git-workflow-and-versioning@sha256:3dfb6c09970f7fca

[![mdr](https://markdownregistry.com/badge/art_xzwbuawvjghzifpt.svg)](https://markdownregistry.com/a/art_xzwbuawvjghzifpt)

Versions

The registry has recorded 2 versions of this file, between Oct 5, 2026 and Oct 28, 2026, about one every 23 days.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_xzwbuawvjghzifpt
GET https://markdownregistry.com/api/v1/resolve?ref=jpeetz/agent-skills/git-workflow-and-versioning
GET https://markdownregistry.com/api/v1/blob/3dfb6c09970f7fca4cbeb9aaa2accf35a383fe745795d405184dac6261c531aa

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from jpeetz/agent-skills

Every file in jpeetz/agent-skills

Other files named git-workflow-and-versioning

Browse by kind, by grade A, or by owner.