git-workflow-and-versioning SKILL.md skillA

This file is byte-identical to the first copy the registry indexed, one of 3 indexed copies. Same content hash, so the same checks give both the same grade.

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

mdr add naimkatiman/continuous-improvement/git-workflow-and-versioning@git:20260507.4a6727c

Pins git:20260507.4a6727c in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

naimkatiman/continuous-improvement

Path

third-party/addy-agent-skills/skills/git-workflow-and-versioning/SKILL.md

Versions recorded

1

Latest version

git:20260507.4a6727c, committed May 7, 2026

Size

10,530 bytes

Repository stars

9

License

MIT

Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, or when you need to organize work across multiple parallel streams.

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)
```

This is the recommended default. Teams using gitflow or long-lived branches can adapt the principles (atomic commits, small changes, descriptive messages) to their branching model — the commit discipline matters more than the specific branching strategy.
…

Read the whole file at its exact version.

How to install

mdr add naimkatiman/continuous-improvement/git-workflow-and-versioning@sha256:b1a84eac7a47f6e2

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

Versions

The registry has recorded 1 version of this file, committed on May 7, 2026.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_favjhragnza7kiwo
GET https://markdownregistry.com/api/v1/resolve?ref=naimkatiman/continuous-improvement/git-workflow-and-versioning
GET https://markdownregistry.com/api/v1/blob/b1a84eac7a47f6e2985a27733137d862fcdeb552eefe2bd17629e1f3c20e0e97

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 naimkatiman/continuous-improvement

Every file in naimkatiman/continuous-improvement

Other files named git-workflow-and-versioning

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