What is common-git-collaboration?

A set of Git version-control rules for commits, branches, pull requests, and repository security. Git records code changes and supports collaboration between developers.

Naming branches, writing commits, preparing pull requests, rebasing feature branches, resolving conflicts, and checking changes before merging.

It keeps changes easier to review and the main code line stable, while reducing accidental exposure of secrets and messy history.

common-git-collaboration — Skill for Claude Code and Codex by HoangNgu

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 HoangNguyen0403/agent-skills-standard --skill common-git-collaboration

Clone the repo

git clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standard

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/hoangnguyen0403/agent-skills-standard/common-git-collaboration/github.svg)](https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/common-git-collaboration)

Your own site

<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/common-git-collaboration"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/common-git-collaboration/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/hoangnguyen0403/agent-skills-standard/common-git-collaboration"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/common-git-collaboration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 523 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.00040	$0.00523
Opus 5	$0.00020	$0.00262
Sonnet 5	$0.00008	$0.00105
Haiku 4.5	$0.00004	$0.00052

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

Security

Grade A, and why

common-git-collaboration 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 12d 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.

.agents/skills/common/common-git-collaboration/SKILL.md · 56 lines

What it actually says

Git & Collaboration

Priority: P0 (CRITICAL)

1. Write Conventional Commits

Format: <type>(<scope>): <description> (e.g., feat(auth): add login validation).
Types: feat, fix, docs, style, refactor, perf, test, chore.
Use imperative mood: "add feature" not "added feature".
One commit = one logical change — no mega-commits.

See implementation examples for conventional commit examples.

2. Manage Branches

Name with prefixes: feat/, fix/, hotfix/, refactor/, docs/.
Create new branch for every task to keep main stable and deployable.
Never push directly to main or develop — use Pull Requests.
Pull before you push to resolve conflicts locally.
Prefer git rebase over merge for linear history on feature branches.
Use git rebase -i to squash messy commits before pushing.

3. Submit Quality Pull Requests

Limit to < 300 lines of code for effective review.
State what changed, why, and how to test. Link issues (Closes #123).
Self-review for obvious errors before requesting peers.
PRs must pass all CI checks (lint, test, build) before merging.

4. Protect Secrets and Metadata

Never commit .env, keys, or certificates — use .gitignore strictly.
Use husky or lefthook for local Git Hooks enforcement.
Tag releases with SemVer (vX.Y.Z) and update CHANGELOG.md.

Anti-Patterns

No direct push to main: All changes via PR, no exceptions.
No mega-commits: One commit = one logical change. Split large ones.
No secrets in history: Use git filter-repo to purge; rotate secret.

References

Clean Linear History & Rebase Examples

Files

What ships with it

2 files 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.

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.

12d ago First seen · 56 lines · 40 tokens per session scan A 91a393a2f346

Subscribe to this mod's changes

common-git-collaboration is a skill published in the GitHub repository HoangNguyen0403/agent-skills-standard (565 stars, last pushed 3d ago), licensed MIT. It adds 40 tokens to every session and 523 once invoked, about $0.0002 per session on Opus 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-30.

Commits Git and workflow React best-practices coding-standards flutter nestjs nextjs

docs

Documentation drift detection and sync via oma-docs. Verify mode finds broken refs in docs//.md, sync mode proposes patches for docs affected by a git diff.

first-fluke/fullstack-starter · 35 tokens

scm

SCM workflow for Git operations (branching/merge/conflict/worktree) plus Conventional Commit execution.

first-fluke/fullstack-starter · 24 tokens

commit

Generate Conventional Commits spec git commits (auto-separate by feature).

first-fluke/fullstack-starter · 16 tokens

oma-scm

SCM (software configuration management) and Git: branching, merges, conflicts, worktrees, baselines, audit readiness, plus Conventional Commits and safe staging.

first-fluke/fullstack-starter · 37 tokens

open-pr

Open a pull request for the Unovis repo with the project's conventions — correct branch off main, the standard commit grouping, and the checklist-style PR body used by the maintainers. Use when asked to open/create/submit a pull request, prepare a branch for review, or write a PR description in this repository.

f5/unovis · 67 tokens

stacking-prs

Create and manage GitHub native Stacked PRs in this repo with the gh stack CLI. Use when asked to stack PRs, split a large change into a stack, add a layer to a stack, restack or rebase a stack, adopt existing branches or PRs into a stack, check out someone else's stack, or land a stack. Covers creating and submitting…

PostHog/posthog · 136 tokens