New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Common Git Collaboration

by HoangNguyen0403 in HoangNguyen0403/agent-skills-standard

Enforce version control best practices for commits, branching, pull requests, and repository security.

MITAuto-check: notesDevelopment

Install Common Git Collaboration

skills CLI
$ npx skills add HoangNguyen0403/agent-skills-standard --skill common-git-collaboration -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install HoangNguyen0403/agent-skills-standard common-git-collaboration --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standard.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/common/common-git-collaboration .claude/skills/common-git-collaboration && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
common-git-collaboration
GitHub stars
572
Token cost
~516 tokens
SKILL.md length
224 words
Files
4 (incl. references)
Skills in repo
211
Repo updated
First seen
Licence
MIT

At a glance

Enforce version control best practices for commits, branching, pull requests, and repository security.

  • Works in 4 steps: Write Conventional Commits → Manage Branches → Submit Quality Pull Requests → …
  • Writing commits
  • SKILL.md covers Priority: P0 (CRITICAL), 1. Write Conventional Commits, 2. Manage Branches and 3. Submit Quality Pull Requests, plus 3 more sections
  • Calls git

What it does

Common Git Collaboration is an agent skill from HoangNguyen0403/agent-skills-standard. Enforce version control best practices for commits, branching, pull requests, and repository security. Use when writing commits, creating branches, merging, or opening pull requests.

Its SKILL.md is about 520 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `evals/evals.json`, `references/CLEAN_HISTORY.md` and `references/implementation.md`).

It sits in Development, covering Git workflow and Pull requests. It works with Git. The repository describes itself as: A collection of Agent Skills Standard and Best Practice for Programming Languages, Frameworks that help our AI Agent follow best practies on frameworks and programming laguages. The licence is MIT.

When your agent uses it

  • Writing commits
  • Creating branches
  • Opening pull requests

Example prompts

  • “/common-git-collaboration”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Write Conventional Commits
  2. Manage Branches
  3. Submit Quality Pull Requests
  4. Protect Secrets and Metadata

What it can do on your machine

Read from SKILL.md and the folder at commit b529c2d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Common Git Collaboration loads about 516 tokens when it runs, and up to ~783 if it reads all its reference files. Until then it costs about 52 tokens; SKILL.md has 224 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~52
When it runs · the whole SKILL.md, loaded when a task matches
~516
With references · SKILL.md plus every file in references/, read only if the agent opens them
~783

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:44
    - Never commit `.env`, keys, or certificates — use `.gitignore` strictly.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from HoangNguyen0403/agent-skills-standard at commit b529c2d, republished under its MIT licence (© HoangNguyen0403). 224 words, ~516 tokens.

Download SKILL.mdSave it as .claude/skills/common-git-collaboration/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
common-git-collaboration
description
Enforce version control best practices for commits, branching, pull requests, and repository security. Use when writing commits, creating branches, merging, or opening pull requests.

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

© HoangNguyen0403, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in skills/common/common-git-collaboration of HoangNguyen0403/agent-skills-standard.

  • SKILL.md
  • evals/evals.json
  • references/CLEAN_HISTORY.md
  • references/implementation.md

Open the folder on GitHubat commit b529c2d

Compare with similar skills

Common Git Collaboration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Common Git Collaboration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Common Git Collaboration this skillHoangNguyen0403/agent-skills-standard572—~516Automated safety check: NotesMIT
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0
Git Branch Namingmakeplane/plane61k—~594Automated safety check: PassAGPL-3.0
Create Pull Request with Work Item IDmakeplane/plane61k—~824Automated safety check: PassAGPL-3.0

Similar skills

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Contributor-First PR Merge

    HKUDS/OpenHarness

    Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

  • Create Pull Request

    cline/cline

    Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed

  • Git Branch Naming

    makeplane/plane

    Names a new Git branch with a type prefix, the lowercased work item ID and a short kebab-case description, so the ID can be extracted later from the branch name.

    61k GitHub stars~594 tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Create Pull Request with Work Item ID

    makeplane/plane

    Opens a pull request for the current branch using the repo's template, a work item ID in the title and a description filled in from the actual diff.

    61k GitHub stars~824 tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Git Workflow and Versioning

    addyosmani/agent-skills

    Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.

    105k GitHub starsUsed in 2 repos~3.5k tokens
    DevelopmentAuto-check: notes

More from HoangNguyen0403/agent-skills-standard

All 211 skills in this repo

  • Subagent-Driven Development

    HoangNguyen0403/agent-skills-standard

    Runs a multi-task implementation plan by sending each task to a fresh implementer subagent, reviewing it independently, then reviewing the whole branch.

    572 GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed

  • draw.io Architecture Diagramming

    HoangNguyen0403/agent-skills-standard

    Draws architecture diagrams as editable draw.io files from a JSON spec, with a fixed house style, one C4 level per diagram and evidence-tagged shapes.

    572 GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed

  • Android Navigation 3 Guide

    HoangNguyen0403/agent-skills-standard

    Implements and migrates to Jetpack Navigation 3 in Compose: NavDisplay, typed route objects, a state-list back stack, deep links, multiple back stacks and dialog scenes.

    572 GitHub stars~687 tokensUpdated yesterday
    Auto-check passed

  • Angular HttpClient Standards

    HoangNguyen0403/agent-skills-standard

    Sets rules for Angular HTTP code: functional interceptors, typed requests, services that own every call, and httpResource for reactive data loading in Angular 17+.

    572 GitHub stars~652 tokensUpdated yesterday
    Auto-check passed

  • Angular Tooling

    HoangNguyen0403/agent-skills-standard

    Angular CLI usage, code generation, build configuration, and bundle optimization.

    572 GitHub stars~743 tokensUpdated yesterday
    Auto-check passed

  • Common Code Review

    HoangNguyen0403/agent-skills-standard

    Conduct high-quality, persona-driven code reviews. An agent skill from HoangNguyen0403/agent-skills-standard.

    572 GitHub stars~772 tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Common Git Collaboration

What does Common Git Collaboration do?

Enforce version control best practices for commits, branching, pull requests, and repository security. Common Git Collaboration is an agent skill from HoangNguyen0403/agent-skills-standard. Enforce version control best practices for commits, branching, pull requests, and repository security.

When should I use Common Git Collaboration?

Common Git Collaboration fits situations like: writing commits; creating branches; opening pull requests.

How do I install Common Git Collaboration in Claude Code?

Run `npx skills add HoangNguyen0403/agent-skills-standard --skill common-git-collaboration -a claude-code`. Or copy the skill folder (skills/common/common-git-collaboration in HoangNguyen0403/agent-skills-standard) into .claude/skills/common-git-collaboration in your project. Claude Code loads it when a task matches its description.

How do I install Common Git Collaboration in Codex?

Run `npx skills add HoangNguyen0403/agent-skills-standard --skill common-git-collaboration -a codex`. Or copy the skill folder (skills/common/common-git-collaboration in HoangNguyen0403/agent-skills-standard) into .agents/skills/common-git-collaboration in your project. Codex loads it when a task matches its description.

Can I use Common Git Collaboration in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add HoangNguyen0403/agent-skills-standard --skill common-git-collaboration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/common-git-collaboration, .gemini/skills/common-git-collaboration, .github/skills/common-git-collaboration and .opencode/skills/common-git-collaboration in your project.

What does Common Git Collaboration need to run?

Going by SKILL.md and its folder, Common Git Collaboration needs the command-line tools its instructions call (git).

Does Common Git Collaboration access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Common Git Collaboration safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Common Git Collaboration use?

Common Git Collaboration is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Common Git Collaboration use?

About 516 tokens (SKILL.md is roughly 2.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 267 tokens, read only when the agent opens those files.

What are the alternatives to Common Git Collaboration?

Skills that share tags, products or a category with Common Git Collaboration: Finishing a Development Branch (obra/superpowers, 297k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Create Pull Request (cline/cline, 70k stars) and Git Branch Naming (makeplane/plane, 61k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Common Git Collaboration?

HoangNguyen0403 (a GitHub user) maintains it in HoangNguyen0403/agent-skills-standard, which has 572 GitHub stars. The repository holds 211 skills in this directory. The repository was last updated on October 9, 2026.

Source: HoangNguyen0403/agent-skills-standard on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.