git-repository

git-repository is a skill for Claude Code from geoffjay/claude-plugins. It costs 45 tokens per session (4,558 once invoked), scanned C, original, MIT.

A guide to organizing Git repositories, branches, submodules, and multi-project codebases. A monorepo is one repository that contains multiple projects; a submodule links one repository inside another.

In plain words
What is it for?
Use it when setting up repositories, choosing Git Flow or trunk-based development, managing monorepos, organizing projects, or planning migrations.
Why use it?
It helps teams choose a repository structure and branching model that fits their projects and collaboration needs.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: positional $N argument.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is cd ../...

Part of the git plugin — 4 skills shipped together

Good fit Use it when setting up repositories, choosing Git Flow or trunk-based development, managing monorepos, organizing projects, or planning migrations.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/geoffjay/claude-plugins
agentmods
npx agentmods add skills/geoffjay/claude-plugins/git-repository

Made for: Claude Code.

Or install git, the plugin that ships this one along with the rest of its 4 skills.

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 git-repository

README.md
[![agentmods](https://agentmods.dev/badge/skills/geoffjay/claude-plugins/git-repository/github.svg)](https://agentmods.dev/skills/geoffjay/claude-plugins/git-repository)
Your own site
<a href="https://agentmods.dev/skills/geoffjay/claude-plugins/git-repository"><img src="https://agentmods.dev/badge/skills/geoffjay/claude-plugins/git-repository/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 git-repository

Your own site · 80×15
<a href="https://agentmods.dev/skills/geoffjay/claude-plugins/git-repository"><img src="https://agentmods.dev/badge/skills/geoffjay/claude-plugins/git-repository.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,558 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00045 $0.04558
Opus 5.5 $0.00018 $0.01823
Sonnet 5.5 $0.00009 $0.00912
Haiku 4.5 $0.00005 $0.00456

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

Security

Grade C, and why

git-repository scanned grade C with 1 finding 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 1mo 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf .git
plugins/utilities/git/skills/git-repository/SKILL.md · 821 lines

How it starts

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

Git Repository Management Skill

This skill provides comprehensive guidance on repository management strategies, branching models, repository organization patterns, and scaling git for large teams and codebases.

When to Use

Activate this skill when:

  • Setting up new repository structure
  • Choosing branching strategy
  • Managing monorepo vs polyrepo
  • Organizing multi-project repositories
  • Implementing submodule or subtree strategies
  • Scaling git for large teams
  • Migrating repository structures
  • Establishing team workflows

Branching Strategies

Git Flow

Branch Structure:

  • main (or master) - Production releases only
  • develop - Integration branch for next release
  • feature/* - Feature development branches
  • release/* - Release preparation branches
  • hotfix/* - Emergency production fixes

Workflow:

# Feature Development
git checkout develop
git checkout -b feature/user-authentication
# Work on feature...
git commit -m "feat: add JWT authentication"
git checkout develop
git merge --no-ff feature/user-authentication
git branch -d feature/user-authentication

# Release Preparation
git checkout develop
git checkout -b release/v1.2.0
# Bump version, update changelog, final testing...
git commit -m "chore: prepare release v1.2.0"

# Deploy Release
git checkout main
git merge --no-ff release/v1.2.0
git tag -a v1.2.0 -m "Release version 1.2.0"
git checkout develop
git merge --no-ff release/v1.2.0
git branch -d release/v1.2.0
git push origin main develop --tags

# Hotfix
git checkout main
git checkout -b hotfix/security-patch
git commit -m "fix: patch security vulnerability"
git checkout main
git merge --no-ff hotfix/security-patch
git tag -a v1.2.1 -m "Hotfix v1.2.1"
git checkout develop
git merge --no-ff hotfix/security-patch
git branch -d hotfix/security-patch
git push origin main develop --tags

Best For:

  • Scheduled releases
  • Multiple production versions
  • Large teams with QA process
  • Products with maintenance windows
  • Enterprise software

Read the full file on GitHub · 821 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. 1mo ago First seen · 821 lines · 45 tokens per session scan C e22d450ff89b

Subscribe to this mod's changes

git-repository is a skill published in the GitHub repository geoffjay/claude-plugins (8 stars, last pushed 11mo ago), licensed MIT. It adds 45 tokens to every session and 4,558 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

mcore-split-pr

Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.

NVIDIA/skills · 25 tokens

shiplog

Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.

aeonfun/aeon · 46 tokens

connect

Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…

nimbalyst/nimbalyst · 101 tokens

llxprt-issue-workflow

Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…

vybestack/llxprt-code · 88 tokens

cuga-github-issues

Create GitHub issues for cuga-agent (bugs, features, epics, designs, and related work) against origin using gh, with epic → feature → issue hierarchy and GraphQL sub-issue linking. Use when the user says create new issues, report a bug, file a bug, feature request, new feature, create an epic, GitHub issue, sub-issue…

cuga-project/cuga-agent · 88 tokens

implement-issue

Implement a Linear brief in a named GitHub repo. Use when the brief skill is implement-issue or the user wants a new branch and draft PR.

CopilotKit/OpenTag · 35 tokens