Git Rules

Essential version control commands for branching, committing, merging, and managing your codebase history with confidence.

4 rules

View Commands

Branch Naming Conventions

Beginner

Standardize Git branch naming patterns with type prefixes, kebab-case formatting, and issue references for consistent, scannable repository navigation.

globs: **/.git/**

branch-naming, conventions, kebab-case, standards

View Rule

Commit Message Conventions

Beginner

Enforce conventional commit message format across your codebase — imperative mood, type prefixes, scope annotations, and body formatting standards for AI coding agents.

globs: **/.git/**, **/.husky/**, **/.commitlintrc*

commit-messages, conventional-commits, formatting, standards

View Rule

.gitignore Best Practices

Beginner

Comprehensive .gitignore rules to prevent committing secrets, build artifacts, OS files, IDE configurations, and other files that don't belong in version control.

globs: **/.gitignore, **/.gitattributes

gitignore, security, secrets, configuration

View Rule

Pull Request Standards

Beginner

Define clear standards for pull request size, descriptions, review process, and merge requirements to maintain code quality and fast review cycles.

globs: **/.github/**, **/.gitlab/**

pull-request, code-review, standards, merge-strategy

View Rule