How do I install the Common Git Collaboration skill?

Run npx skillmds@latest add comeonoliver/common-git-collaboration in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Common Git Collaboration safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Common Git Collaboration?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Common Git Collaboration free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Common Git Collaboration?

ComeOnOliver (@comeonoliver) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Common Git Collaboration by comeonoliver

Name: Common Git Collaboration
Rating: 4.2 (5 reviews)
Author: ComeOnOliver

Common Git Collaboration

Universal standards for version control, branching, and team collaboration. Use when writing commits, creating branches, merging, or opening pull requests. (triggers: commit, branch, merge, pull-request, git)

ComeOnOliver Updated Sep 8, 2026 61 repo stars

File contents

Git & Collaboration

Priority: P0 (OPERATIONAL)

📝 Commit Messages (Conventional Commits)

Format: <type>(<scope>): <description> (e.g., feat(auth): add login validation).
Types: feat (new feature), fix (bug fix), docs, style, refactor, perf, test, chore.
Atomic Commits: One commit = One logical change. Avoid "mega-commits".
Imperative Mood: Use "add feature" instead of "added feature" or "adds feature".

🌿 Branching & History Management

Naming: Use prefixes: feat/, fix/, hotfix/, refactor/, docs/.
Branch for Everything: Create a new branch for every task to keep the main branch stable and deployable.
Main Branch Protection: Never push directly to main or develop. Use Pull Requests.
Sync Early: "Pull Before You Push" to identify and resolve merge conflicts locally.
Prefer Rebase: Use git rebase (instead of merge) to keep a linear history when updating local branches from develop or main.
Interactive Rebase: Use git rebase -i to squash or fixup small, messy commits before pushing to a shared branch.
No Merge Commits: Avoid "Merge branch 'main' into..." commits in feature branches. Always rebase onto the latest upstream.

🤝 Pull Request (PR) Standards

Small PRs: Limit to < 300 lines of code for effective review.
Commit Atomicness: Each commit should represent a single, complete logical change.
Description: State what changed, why, and how to test. Link issues (Closes #123).
Self-Review: Review your own code for obvious errors/formatting before requesting peers.
CI/CD: PRs must pass all automated checks (lint, test, build) before merging.

🛡 Security & Metadata

No Secrets: Never commit .env, keys, or certificates. Use .gitignore strictly.
Git Hooks: Use tools like husky or lefthook to enforce standards locally.
Tags: Use SemVer (vX.Y.Z) for releases. Update CHANGELOG.md accordingly.

📚 References

Clean Linear History & Rebase Examples

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 the secret.

---name: common-git-collaborationdescription: Universal standards for version control, branching, and team collaboration. Use when writing commits, creating branches, merging, or opening pull requests. (triggers: commit, branch, merge, pull-request, git)---# Git & Collaboration## **Priority: P0 (OPERATIONAL)**## 📝 Commit Messages (Conventional Commits)- **Format**: `<type>(<scope>): <description>` (e.g., `feat(auth): add login validation`).- **Types**: `feat` (new feature), `fix` (bug fix), `docs`, `style`, `refactor`, `perf`, `test`, `chore`.- **Atomic Commits**: One commit = One logical change. Avoid "mega-commits".- **Imperative Mood**: Use "add feature" instead of "added feature" or "adds feature".## 🌿 Branching & History Management- **Naming**: Use prefixes: `feat/`, `fix/`, `hotfix/`, `refactor/`, `docs/`.- **Branch for Everything**: Create a new branch for every task to keep the main branch stable and deployable.- **Main Branch Protection**: Never push directly to `main` or `develop`. Use Pull Requests.- **Sync Early**: "Pull Before You Push" to identify and resolve merge conflicts locally.- **Prefer Rebase**: Use `git rebase` (instead of merge) to keep a linear history when updating local branches from `develop` or `main`.- **Interactive Rebase**: Use `git rebase -i` to squash or fixup small, messy commits before pushing to a shared branch.- **No Merge Commits**: Avoid "Merge branch 'main' into..." commits in feature branches. Always rebase onto the latest upstream.## 🤝 Pull Request (PR) Standards- **Small PRs**: Limit to < 300 lines of code for effective review.- **Commit Atomicness**: Each commit should represent a single, complete logical change.- **Description**: State what changed, why, and how to test. Link issues (`Closes #123`).- **Self-Review**: Review your own code for obvious errors/formatting before requesting peers.- **CI/CD**: PRs must pass all automated checks (lint, test, build) before merging.## 🛡 Security & Metadata- **No Secrets**: Never commit `.env`, keys, or certificates. Use `.gitignore` strictly.- **Git Hooks**: Use tools like `husky` or `lefthook` to enforce standards locally.- **Tags**: Use SemVer (`vX.Y.Z`) for releases. Update `CHANGELOG.md` accordingly.## 📚 References- [Clean Linear History & Rebase Examples](references/CLEAN_HISTORY.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 the secret.

Frequently asked questions