git-workflow-and-versioning skillA

This file is byte-identical to the first copy the registry indexed, one of 5 copies on public GitHub. Same content hash, same audit grade.

git-workflow-and-versioning is agent-read markdown (skill) from nota-america/forgecat-agent-profiles: Structures git workflow practices. Use when making any code change. Use when 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 when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump, tagging, or writing a changelog..

Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns 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 nota-america/forgecat-agent-profiles/git-workflow-and-versioning@git:20260916.3a6b22e

mdr add nota-america/forgecat-agent-profiles/git-workflow-and-versioning@sha256:b7465d187935c525

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

Versions

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_o6sht56qntgerx7a
GET https://markdownregistry.com/api/v1/resolve?ref=nota-america/forgecat-agent-profiles/git-workflow-and-versioning
GET https://markdownregistry.com/api/v1/blob/b7465d187935c52546d39fdc7bd6ac36d94eda25a9500ef8c18b767d2eb116ea

Your agent 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.

More from nota-america/forgecat-agent-profiles

Every file in nota-america/forgecat-agent-profiles

Other files named git-workflow-and-versioning

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