Git Workflow SKILL.md skillA

Git Workflow from nxtg-ai/forge-plugin is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add nxtg-ai/forge-plugin/Git Workflow@git:20261007.7682d9b

Pins git:20261007.7682d9b in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: nxtg-ai/forge-plugin
Path: plugins/nxtg-forge/skills/git-workflow/SKILL.md
Versions recorded: 4
Latest version: git:20261007.7682d9b, committed Oct 7, 2026
First version recorded: Feb 7, 2026
Size: 7,322 bytes
Repository stars: 6
License: MIT

Trunk-based git workflow for NXTG-Forge — branching strategy, commit conventions, PR practices, rebase/conflict resolution, and how the plugin's own hooks guard git operations. Use when creating a feature branch, writing a commit message or PR, rebasing onto main, resolving merge conflicts, choosing a merge strategy, recovering from a bad commit/reset/detached HEAD, or when a git push is blocked by a security hook.

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 Branching Strategy

NXTG-Forge uses **trunk-based development**: `main` stays always-deployable, work happens
on short-lived feature branches, and changes land via squash-merged PRs. This SKILL.md is
the lean operating guide; deep tables (commit/PR conventions, recovery recipes) live in the
linked reference files.

## Branch strategy

- **`main`** — always deployable, protected, requires PR + passing CI. Single source of truth.
- **Feature branches** — short-lived (1–3 days), single-purpose, named `type/description`:
  `feat/user-authentication`, `fix/login-validation-bug`, `refactor/state-migration`,
  `docs/api-guide`, `chore/dep-bump`.
- **No long-lived branches** — no `develop`, no `release/*`, no `hotfix/*`. Fix directly
  from `main` on a `fix/*` branch. (Reversing this needs an ADR.)

## The core loop

```bash
# 1. Branch off fresh main
git checkout main && git pull origin main
git checkout -b feat/user-authentication

# 2. Work → stage EXPLICIT paths (never `git add -A` / `git add .`) → commit
git add src/auth/ tests/auth.test.mjs
git commit -m "feat: add JWT auth middleware"

# 3. Stay current — rebase, don't merge main in
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add nxtg-ai/forge-plugin/Git Workflow@sha256:9b52d55653c17df6

The line at the top of this page pins the label git:20261007.7682d9b, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

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

3 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 4 versions of this file, between Feb 7, 2026 and Oct 7, 2026, about one every 81 days.

version	committed	commit	size	audit
git:20261007.7682d9b latest	2026-10-07	7682d9b	7,322 B	A	view · diff
git:20260714.4fd0952	2026-07-14	4fd0952	7,307 B	A	view · diff
git:20260714.061716b	2026-07-14	061716b	15,085 B	A	view · diff
git:20260207.88c1f6e	2026-02-07	88c1f6e	15,065 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (7322 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag

Source

GitHub

nxtg-ai/forge-plugin · 6 stars · license MIT · pushed 2026-10-15 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_fcrhqvialjzicncz
GET https://markdownregistry.com/api/v1/resolve?ref=nxtg-ai/forge-plugin/Git Workflow
GET https://markdownregistry.com/api/v1/blob/9b52d55653c17df6b56d0b07ecd8556d36800000080c2d250308fa282cddf5b8

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 nxtg-ai/forge-plugin

CLAUDE.md CLAUDE.md file

nxtg-ai/forge-plugin · CLAUDE.md

git:20261015.6ff23ad · audit B · 6 stars

Backend Master Agent SKILL.md skill

nxtg-ai/forge-plugin · plugins/nxtg-forge/skills/agent-backend-master/SKILL.md · Backend implementation playbook — API endpoints, database models/migrations, auth, query optimization, and the…