What is git-workflow?

A set of guidelines for managing Git changes, including branch choices, commit message conventions, code review, release automation, and monorepo CI. A monorepo is one repository containing multiple projects or packages.

Use it to design a branching model, enforce Conventional Commits, configure commit hooks, automate versioned releases, set CODEOWNERS, or organize continuous integration for a monorepo.

It helps teams choose a consistent way to develop, review, release, and test code instead of making these decisions separately for each project.

git-workflow — Skill for Codex by san-npm: A set of guidelines for managing Git changes, including…

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/san-npm/skills-ws/git-workflow

Any agent

npx skills add san-npm/skills-ws --skill git-workflow

Clone the repo

git clone --depth 1 https://github.com/san-npm/skills-ws

Made for: Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/san-npm/skills-ws/git-workflow.svg)](https://agentmods.dev/skills/san-npm/skills-ws/git-workflow)

Your own site

<a href="https://agentmods.dev/skills/san-npm/skills-ws/git-workflow"><img src="https://agentmods.dev/badge/skills/san-npm/skills-ws/git-workflow.svg" alt="Measured on agentmods" height="20"></a>

Per session 77 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,913 The whole file, excluding the scripts and references it only reads on demand.

Security scan C 2 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00077	$0.03913
Opus 5	$0.00039	$0.01956
Sonnet 5	$0.00015	$0.00783
Haiku 4.5	$0.00008	$0.00391

Measured 5d ago against content hash 99f11500bd50, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade C, and why

git-workflow scanned grade C with 2 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Reaches for credential fileshighPrivilege escalation

SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.

git config --global user.signingkey ~/.ssh/id_ed25519.pub

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

skills/git-workflow/SKILL.md · 396 lines

How it starts

The opening of the file, as written. The whole thing — 396 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Git Workflow

Branching Strategies

Strategy	Best For	Branch Lifetime	Release Cadence
Trunk-Based	CI/CD, small teams	Hours	Continuous
GitHub Flow	SaaS, web apps	Days	On merge
GitFlow	Versioned software, mobile	Weeks	Scheduled

Trunk-Based (Recommended for most teams)

main ←── short-lived feature branches (< 2 days)
  └── release/* (cut when ready, hotfix → cherry-pick back)

All developers commit to main (or merge within 24h)
Use feature flags for incomplete work, not long-lived branches
CI must pass on every commit to main

GitHub Flow

git checkout -b feat/user-avatars
# work, commit, push
gh pr create --base main --fill
# review → squash merge → auto-deploy

GitFlow (when you need it)

main ← tagged releases only
develop ← integration branch
  ├── feature/* → develop
  ├── release/* → main + develop
  └── hotfix/*  → main + develop

Commit Conventions (Conventional Commits)

<type>(<scope>): <description>

[optional body]

[optional footer(s)]

Type	SemVer Bump	Example
`fix`	PATCH	`fix(auth): handle expired refresh tokens`
`feat`	MINOR	`feat(api): add pagination to /users`
`feat!` or `BREAKING CHANGE:`	MAJOR	`feat(api)!: remove v1 endpoints`
`chore`, `docs`, `ci`, `refactor`, `test`, `perf`	none	`ci: add Node 24 to matrix`

Enforce with commitlint — see the Git Hooks section below for the correct Husky v9+ wiring (the old npx husky add ... command was removed in Husky v9).

Git Hooks (Husky + lint-staged + commitlint)

Husky v9+ changed the setup: there is no husky add/husky install anymore. Run husky init, then write hook files directly (a hook is just a shell script; no #!/bin/sh shebang or husky.sh sourcing line is needed in v9+).

# 1. Install tooling
npm i -D husky lint-staged @commitlint/cli @commitlint/config-conventional

# 2. Scaffold .husky/ and add the "prepare" script to package.json
npx husky init        # creates .husky/pre-commit (with "npm test") + sets "prepare": "husky"

# 3. commitlint config (commitlint.config.mjs — ESM is the current default)
printf "export default { extends: ['@commitlint/config-conventional'] };\n" > commitlint.config.mjs

Read the full file on GitHub · 396 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

agents/openai.yaml 195 B

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

5d ago First seen · 396 lines · 77 tokens per session scan C 99f11500bd50

Subscribe to this mod's changes

git-workflow is a skill published in the GitHub repository san-npm/skills-ws (2 stars, last pushed 20d ago), licensed MIT. It adds 77 tokens to every session and 3,913 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it C with 2 findings (reaches for credential files, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Commits Git and workflow Releases

github-automation

GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.

ruvnet/ruflo · 61 tokens

git-workflow