How do I install the Git Conventions skill?

Run npx skillmds@latest add sordi-ai/git-conventions 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 Git Conventions safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Git Conventions?

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 Git Conventions free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Git Conventions?

sordi-ai (@sordi-ai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Git Conventions by sordi-ai — Agent Skill

Name: Git Conventions
Author: sordi-ai

File contents

Sub-Skill: Git & Workflow Conventions

Purpose: Consistent commit history, clean branches, no merge conflicts through discipline. Rules that work in teams of 2–20 developers.

Rules

Commit Messages (Conventional Commits)

Format: <type>(<scope>): <description> — always lowercase, no period at the end.
- Types: feat, fix, refactor, test, docs, chore, perf, ci
- Example: feat(auth): add JWT refresh token rotation
Description in imperative mood. add feature not added feature or adds feature.
Scope is the affected module name. fix(user-service): handle null email — not fix(backend).
Mark breaking changes with !. feat(api)!: remove deprecated v1 endpoints
Body for non-obvious changes. Explains the why, not the what.

Branching

Branch names: <type>/<ticket-id>-<short-description> — e.g. feat/PROJ-123-user-export.
Feature branches live max. 2 days. Longer → rebase daily onto main.
No direct push to main or develop. Always through a pull request.
Delete branch before PR merge. Clean up merged branches from remote.

Pull Requests

PR title = commit message of the squash commit. Consistency between PR and git log.
Max. 400 lines diff per PR. Larger → split. Reviewers cannot meaningfully review more than 400 lines.
Self-review before opening a PR. Read through once yourself, fix obvious mistakes.

Merge Strategy

Squash-merge for feature branches. Clean linear history on main.
Merge commit for release branches. So release points remain visible.
git rebase -i before PR for clean commits. Squash WIP commits together.

Why This Sub-Skill Earns Stars

The agent automatically creates correct commit messages and branch names. No manual corrections, no discussions in review about formatting.

---name: git-conventionsdescription: Apply when committing, branching, or opening a pull request. Conventional commit format, branch naming, PR scope.license: MIT---# Sub-Skill: Git & Workflow Conventions**Purpose:** Consistent commit history, clean branches, no merge conflicts through discipline.Rules that work in teams of 2–20 developers.---## Rules### Commit Messages (Conventional Commits)1. **Format:** `<type>(<scope>): <description>` — always lowercase, no period at the end. - Types: `feat`, `fix`, `refactor`, `test`, `docs`, `chore`, `perf`, `ci` - Example: `feat(auth): add JWT refresh token rotation`2. **Description in imperative mood.** `add feature` not `added feature` or `adds feature`.3. **Scope is the affected module name.** `fix(user-service): handle null email` — not `fix(backend)`.4. **Mark breaking changes with `!`.** `feat(api)!: remove deprecated v1 endpoints`5. **Body for non-obvious changes.** Explains the *why*, not the *what*.### Branching6. **Branch names:** `<type>/<ticket-id>-<short-description>` — e.g. `feat/PROJ-123-user-export`.7. **Feature branches live max. 2 days.** Longer → rebase daily onto `main`.8. **No direct push to `main` or `develop`.** Always through a pull request.9. **Delete branch before PR merge.** Clean up merged branches from remote.### Pull Requests10. **PR title = commit message of the squash commit.** Consistency between PR and git log.11. **Max. 400 lines diff per PR.** Larger → split. Reviewers cannot meaningfully review more than 400 lines.12. **Self-review before opening a PR.** Read through once yourself, fix obvious mistakes.### Merge Strategy13. **Squash-merge for feature branches.** Clean linear history on `main`.14. **Merge commit for release branches.** So release points remain visible.15. **`git rebase -i` before PR for clean commits.** Squash WIP commits together.---## Why This Sub-Skill Earns StarsThe agent automatically creates correct commit messages and branch names.No manual corrections, no discussions in review about formatting.

Frequently asked questions

Git Conventions