Skills Guide

Git - Version Control Standards

VerifiedSafe

Establishes Git version control standards: conventional commit messages, branching strategy (main, develop, feat/fix), and atomic commit principles. Helps maintain a clean, semantic history that is easy to navigate and understand.

Download and use
Sby Skills Guide Bot
DevelopmentBeginner
6/2/2026
Claude CodeCursorWindsurfCopilotCodex
#git#commit-conventions#branching-strategy#version-control

Recommended for

Backend developerClaude CodeCode reviewFrontend developerCursorCopilot

Automated summary

Establishes standards for Git usage, including conventional commit messages, branching strategies, and conflict resolution.

Strengths

  • Enforces atomic commits with structured messages (Conventional Commits)
  • Provides clear rules for workflows and branch naming
  • Includes a pre-commit checklist to avoid common mistakes

Limitations

  • Mandates a specific convention that may not fit all teams
  • Does not cover advanced operations like rebase or cherry-pick
  • May be overly rigid for personal or very small projects
When to use it

Use this skill when working on a shared codebase with multiple contributors and you want to maintain a clean, traversable history.

When not to use it

Avoid if your team already follows a different commit convention or if the project is solo and history strictness is not needed.

Security analysis

Safe
Quality score90/100

The skill provides only guidelines and standards for using Git, with no embedded commands or instructions that would execute harmful operations. It explicitly advises against committing sensitive data and promotes safe practices.

No concerns found

How this analysis is made

Examples

Commit message for a feature
Write a commit message following conventional commits for implementing JWT token validation in the authentication module.
Branching strategy for a bug fix
Suggest a branching strategy and branch name for fixing an issue where search results are not handled gracefully when empty.
Pre-commit review
Check my current git status and staged files, and help me stage only relevant changes while ignoring node_modules and .env files before committing.

name: git description: Standards for version control, commit messages, and branching strategy allowed-tools: run_command version: 1.0 priority: CRITICAL

Git - Version Control Standards

CRITICAL SKILL - Maintain a clean, traversable, and semantic history.

Core Principles

| Principle | Rule | |-----------|------| | Atomic Commits | One logical change per commit (e.g., "Fix bug" vs "Fix bug and add feature") | | Conventional Commits | Use structured messages (feat, fix, docs, refactor, etc.) | | Clean History | Don't commit broken code. Squash WIP commits before merging. | | Ignore Artifacts | Never commit derived files (builds, local configs, secrets). |

Commit Message Convention

Follow the Conventional Commits specification:

<type>(<scope>): <subject>

<body>

<footer>

Types

| Type | Description | |------|-------------| | feat | A new feature | | fix | A bug fix | | docs | Documentation only changes | | style | Changes that do not affect the meaning of the code (white-space, formatting, etc) | | refactor | A code change that neither fixes a bug nor adds a feature | | perf | A code change that improves performance | | test | Adding missing tests or correcting existing tests | | chore | Changes to the build process or auxiliary tools and libraries |

Examples

Good:

  • feat(auth): implement jwt token validation
  • fix(search): handle empty result sets gracefully
  • docs(readme): update installation instructions

Bad:

  • update code
  • fix bug
  • wip

Workflow Rules

  1. Before Committing:

    • Check git status to see what will be staged.
    • Run git diff to review changes line-by-line.
    • Ensure sensitive data (API keys) is NOT included.

  2. Branching (if applicable):

    • main / master: Stable production code.
    • develop / dev: Integration branch.
    • feat/feature-name: Feature branches.
    • fix/issue-description: Bug fix branches.

  3. Handling Conflicts:

    • Pull changes from remote often to minimize conflicts.
    • Resolve conflicts manually, understanding both sides of the change.

Common Commands Checklist

| Action | Command | |--------|---------| | Check Status | git status | | View Changes | git diff | | Stage Files | git add <file> (Avoid git add . unless sure) | | Commit | git commit -m "type(scope): message" | | Log | git log --oneline --graph --decorate --all |

🔴 Self-Check Before Committing

Ask yourself:

  1. Does this commit break the build?
  2. Did I accidentally include node_modules, venv, or .env?
  3. Is the commit message descriptive enough for someone else to understand 6 months from now?

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/git-version-control-standards-mmio70uq/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/git-version-control-standards-mmio70uq' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/git-version-control-standards-mmio70uq/download' --output '.skill-downloads/git-version-control-standards-mmio70uq/SKILL.md.part' && mv '.skill-downloads/git-version-control-standards-mmio70uq/SKILL.md.part' '.skill-downloads/git-version-control-standards-mmio70uq/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): run_command

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/git-version-control-standards-mmio70uq/SKILL.md' && test -s '.skill-downloads/git-version-control-standards-mmio70uq/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/git' && cp -R '.skill-downloads/git-version-control-standards-mmio70uq' '.claude/skills/git'

Cursor
test -f '.skill-downloads/git-version-control-standards-mmio70uq/SKILL.md' && test -s '.skill-downloads/git-version-control-standards-mmio70uq/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/git' && cp -R '.skill-downloads/git-version-control-standards-mmio70uq' '.cursor/skills/git'

Codex
test -f '.skill-downloads/git-version-control-standards-mmio70uq/SKILL.md' && test -s '.skill-downloads/git-version-control-standards-mmio70uq/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/git' && cp -R '.skill-downloads/git-version-control-standards-mmio70uq' '.agents/skills/git'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/git-version-control-standards-mmio70uq'

openskills read 'git-version-control-standards-mmio70uq'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/git-version-control-standards-mmio70uq/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

React Hook Form Best Practices

Development

Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.

Claude CodeCursorWindsurf+2intermediateSafe 108,623
Skills Guide Bot

Emotion to Mantine Migration

Development

Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.

Claude CodeCursorWindsurf+1intermediateSafe 48,981
Skills Guide Bot

Scope Creep Detector

Development

Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.

Claude CodeCursorCodexintermediateSafe 135,015
Skills Guide Bot