What is git-workflow-and-versioning?

A Git workflow guide covering branches, commit messages, pull requests, and software version numbers. Git is a tool for tracking code changes, while a pull request is a proposed change submitted for review.

Use it to name branches, write consistent commits, split large pull requests, and prepare version tags or release changes.

It keeps project history understandable and makes changes easier to review, debug, revert, and connect to releases.

git-workflow-and-versioning — Skill by vignesh2027/AI-AGENT-SKILLS

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.

Any agent

npx skills add vignesh2027/AI-AGENT-SKILLS --skill git-workflow-and-versioning

Clone the repo

git clone --depth 1 https://github.com/vignesh2027/AI-AGENT-SKILLS

Made for: Claude Code, 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/vignesh2027/ai-agent-skills/git-workflow-and-versioning/github.svg)](https://agentmods.dev/skills/vignesh2027/ai-agent-skills/git-workflow-and-versioning)

Your own site

<a href="https://agentmods.dev/skills/vignesh2027/ai-agent-skills/git-workflow-and-versioning"><img src="https://agentmods.dev/badge/skills/vignesh2027/ai-agent-skills/git-workflow-and-versioning/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/vignesh2027/ai-agent-skills/git-workflow-and-versioning"><img src="https://agentmods.dev/badge/skills/vignesh2027/ai-agent-skills/git-workflow-and-versioning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

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

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.00021	$0.00610
Opus 5.5	$0.00008	$0.00244
Sonnet 5.5	$0.00004	$0.00122
Haiku 4.5	$0.00002	$0.00061

Measured 2mo ago against content hash 3dcadd82729f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

git-workflow-and-versioning scanned grade A with 0 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 2mo 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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/git-workflow-and-versioning/SKILL.md · 80 lines

How it starts

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

Overview

Git history is documentation. A clear commit history enables fast debugging, safe reverts, and meaningful changelogs. This skill enforces the habits that make git useful as a tool rather than just a backup system.

When to Use

Before starting any branch
Before committing changes
Before creating a PR
When tagging a release

Process

Step 1: Branch naming

Use: <type>/<description> — e.g., feat/user-search, fix/login-redirect, chore/update-deps Types: feat, fix, docs, chore, refactor, perf, test

Step 2: Commit messages

Follow Conventional Commits:

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

[optional body]
[optional footer]

Examples:

feat(auth): add OAuth2 login with Google
fix(api): handle null user_id in /profile endpoint
perf(db): add index on users.email column

Rules:

Description is imperative mood ("add" not "added")
Under 72 characters
One logical change per commit
Reference ticket: Closes #123

Step 3: Keep PRs small

A PR should be reviewable in under 30 minutes. If it takes longer, it's too big. Split it.

One logical change per PR
No PRs with 500+ line diffs (with rare exceptions)
No WIP code in a PR

Step 4: PR description

Every PR must have:

What changed (not a list of files, but a description of the change)
Why it changed
How to test it
Screenshots for UI changes
Link to the ticket

Step 5: Semantic versioning

MAJOR.MINOR.PATCH

MAJOR: breaking change (removing an API, changing a contract)
MINOR: backward-compatible new feature
PATCH: backward-compatible bug fix

Tag releases: git tag v1.2.3 -m "Release 1.2.3"

Step 6: Git hygiene

Never force push to main/master
Never commit secrets (use pre-commit hooks: gitleaks, detect-secrets)
Rebase feature branches on main before merging (or squash)
Delete branches after merge

Verification Requirements

Branch follows naming convention
Commits follow Conventional Commits format
PR has description with: what, why, how to test
PR is reviewable in under 30 minutes
No secrets committed (pre-commit hook confirms)
Release tagged with semantic version

Read the full file on GitHub · 80 lines

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.

2mo ago First seen · 80 lines · 21 tokens per session scan A 3dcadd82729f

Subscribe to this mod's changes

git-workflow-and-versioning is a skill published in the GitHub repository vignesh2027/AI-AGENT-SKILLS (2 stars, last pushed 2mo ago), licensed MIT. It adds 21 tokens to every session and 610 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Claude Code Git and workflow agent-skills ai-agents coding-agent cursor-ai developer-tools

git-workflow-and-versioning next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
git-workflow-and-versioningvignesh2027/AI-AGENT-SKILLS	Skill	2	2mo ago	MIT	A	21	Claude Code, Codex
autofix-prQwenLM/qwen-code	Skill	29k	today	Apache-2.0	A	141	Claude Code
repo-hygieneQwenLM/qwen-code	Skill	29k	today	Apache-2.0	A	48	Claude Code, Codex
create-issueQwenLM/qwen-code	Skill	29k	today	Apache-2.0	A	26	Claude Code
codex-pr-bodyopeninterpreter/openinterpreter	Skill	69k	3d ago	Apache-2.0	A	17	Codex
update-v8-versionopeninterpreter/openinterpreter	Skill	69k	3d ago	Apache-2.0	A	86	Codex
contributor-onboardingHmbown/CodeWhale	Skill	41k	6d ago	MIT	A	57	Claude Code, Codex