Common Git Collaboration Agent Skill

Enforce version control best practices for commits, branching, pull requests, and repository security. Use when writing commits, creating branches, merging, or opening pull requests.

784 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

536

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/HoangNguyen0403/agent-skills-standard --skill common-git-collaboration

What comes with it

1 067 bytes besides the instruction

references/CLEAN_HISTORY.md

references/implementation.md

The instruction itself

8 sections, as written by the author

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

Other skills for the same job

different authors, same section of the catalogue

Git Commit

by github

vendor ×3

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

Comprehensive GitHub code review with AI-powered swarm coordination

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

2k tokens

Verification & Quality Assurance

by Microck

×2

Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.

GitHub CLI (gh) comprehensive reference for repositories, issues, pull requests, Actions, projects, releases, gists, codespaces, organizations, extensions, and all GitHub operations from the command line.

GitHub CLI - manage repositories, issues, pull requests, actions, releases, and more from the command line.

1k tokens

Codebase Cleanup Refactor Clean

by ComeOnOliver

×2

You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.

9k tokens

Codebase Cleanup Tech Debt

by ComeOnOliver

×2

You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create acti

6k tokens

How to use it

Copy the folder

Take hoangnguyen0403/common-git-collaboration from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.