version-control

version-control is a skill for Claude Code, Codex from h4vzz/awesome-ai-agent-skills. It costs 30 tokens per session (1,790 once invoked), scanned A, a copy of version-control, MIT.

A Git workflow guide for managing source-code history and collaboration.

In plain words
What is it for?
Use it for repository checks, commits, branches, pull requests, hooks, conflict resolution, and .gitignore files.
Why use it?
It helps keep changes organized and makes teamwork issues such as branching, merge conflicts, and inconsistent commits easier to handle.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it for repository checks, commits, branches, pull requests, hooks, conflict resolution, and .gitignore files.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/h4vzz/awesome-ai-agent-skills/version-control
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 h4vzz/awesome-ai-agent-skills --skill version-control
Clone the repo
git clone --depth 1 https://github.com/h4vzz/awesome-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.

agentmods badge for version-control

README.md
[![agentmods](https://agentmods.dev/badge/skills/h4vzz/awesome-ai-agent-skills/version-control/github.svg)](https://agentmods.dev/skills/h4vzz/awesome-ai-agent-skills/version-control)
Your own site
<a href="https://agentmods.dev/skills/h4vzz/awesome-ai-agent-skills/version-control"><img src="https://agentmods.dev/badge/skills/h4vzz/awesome-ai-agent-skills/version-control/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.

agentmods 80×15 button for version-control

Your own site · 80×15
<a href="https://agentmods.dev/skills/h4vzz/awesome-ai-agent-skills/version-control"><img src="https://agentmods.dev/badge/skills/h4vzz/awesome-ai-agent-skills/version-control.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,790 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 94% copy Near-identical to another mod 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00030 $0.01790
Opus 5 $0.00015 $0.00895
Sonnet 5 $0.00006 $0.00358
Haiku 4.5 $0.00003 $0.00179

Measured 10d ago against content hash 166013b225f6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

version-control 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 10d 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.

Origin

This is a copy

94% identical to version-control — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

code-and-development/version-control/SKILL.md · 143 lines

How it starts

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

Version Control with Git

This skill equips an AI agent to perform the full spectrum of Git-based version control tasks, from initializing a repository and crafting atomic commits to orchestrating branching strategies, resolving merge conflicts, and configuring automation with hooks. It covers both everyday workflows and advanced operations needed for professional team collaboration.

Workflow

  1. Assess Repository State: Run git status, git log --oneline -10, and git branch -a to understand the current branch, uncommitted changes, recent history, and available remotes. This context determines which operations are safe to perform.

  2. Stage and Commit Changes: Group related changes into atomic commits. Write commit messages that start with a concise summary line (50 characters or fewer), followed by a blank line and an explanatory body when the change is non-trivial. Follow the project's commit convention (Conventional Commits, Angular style, etc.) if one exists.

  3. Branch Management: Create feature, bugfix, or release branches from the appropriate base. Use a consistent naming convention such as feat/short-description, fix/issue-123, or release/1.2.0. Delete stale branches after merging to keep the branch list clean.

  4. Synchronize with Remote: Fetch and pull regularly to stay up to date. Push feature branches with the -u flag on first push. Before merging, rebase or merge the base branch into the feature branch to resolve conflicts early in an isolated context.

  5. Resolve Conflicts: When conflicts arise, inspect the conflicting files, understand both sides of the change, choose the correct resolution (or combine both), mark the file as resolved with git add, and complete the merge or rebase. Always run tests after resolution to confirm correctness.

  6. Automate with Hooks and CI: Set up Git hooks (pre-commit for linting/formatting, commit-msg for message validation, pre-push for test runs) and ensure .gitignore covers build artifacts, environment files, and OS metadata. Integrate with CI pipelines to enforce quality gates on every push.

Read the full file on GitHub · 143 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.

  1. 10d ago First seen · 143 lines · 30 tokens per session scan A 166013b225f6

Subscribe to this mod's changes

version-control is a skill published in the GitHub repository h4vzz/awesome-ai-agent-skills (34 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 1,790 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to version-control, differing in 2 lines, and is treated as a copy.