Run any Skill in Manus with one click

git-conventions

Stars1

Forks1

UpdatedMay 2, 2026 at 12:05

Git command rules, commit message conventions, and safe usage patterns. Use when the user asks to commit, create a branch, check differences, write a commit message, or perform any git operation. Also use when discussing version control workflows or git safety.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

cboudereau

cboudereau/dotfiles

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	git-conventions
description	Git command rules, commit message conventions, and safe usage patterns. Use when the user asks to commit, create a branch, check differences, write a commit message, or perform any git operation. Also use when discussing version control workflows or git safety.

Git Conventions

When to use

User asks to commit, stage, diff, or perform any git operation
User asks to create a branch or write a commit message
User asks to check differences with a previous version
User mentions "git", "commit", "branch", "diff", or "version control"
User is ready to commit after completing a task

Overview

Rules for safe and consistent git usage.

Rules

Before committing, the code must compile and tests must be successful without failing / ignored tests.

Command rules

Never use the command push.
Never use the option force --force.
Never amend commit to modify files, prefer adding more commits (fix commit) and explain the error/reason.
Before running a new git command, ask to add it in the allow list.
Do not hesitate to use git when checking differences with the previous version.
A task should be committed when tests pass (with assertions) and code coverage is verified.

Commit message

A git commit message must start with:

feat: for feature
fix: when fixing the codebase
refac: for refactoring, mostly to prepare or finish a feat
chore: to cleanup the codebase, removing dead code
doc: when touching to .md files or documentation
test: when touching test only

More from this repository

same repository

code-review

cboudereau/dotfiles

Code review principles and checklist for reviewing any codebase regardless of language. Use when the user asks to review code, perform a code review, assess a pull request, or evaluate code quality across design, tests, performance, security, and correctness.

2026-05-201

plan

cboudereau/dotfiles

Planning skill for complex, multi-session work. Use when the user enters plan mode, asks to plan a feature, design a system, create a workspace, write a design doc, or when the problem requires structured analysis before implementation.

2026-05-091

tdd

cboudereau/dotfiles

Test Driven Development methodology with acceptance tests and unit tests. Use when the user asks to write tests, add test coverage, implement a feature using TDD, create a failing test first, or when discussing red-green-refactor, test-first development, or test strategy.

2026-05-031

code-quality

cboudereau/dotfiles

Code quality principles for writing clean, maintainable software. Use when reviewing code, refactoring, discussing best practices, improving readability, reducing complexity, or when the user mentions code quality, clean code, SOLID, DRY, or maintainability.

2026-05-021

dotnet-software-engineer

cboudereau/dotfiles

.NET Software Engineer persona using TDD, Domain Driven Design, and C#. Use when working on .NET, C#, F#, ASP.NET, or dotnet projects, or when the user asks about software architecture, domain modeling, clean architecture, hexagonal architecture, or DDD patterns like aggregates, value objects, entities, and repositories.

2026-05-021

rust-software-engineer

cboudereau/dotfiles

Rust Software Engineer persona using TDD, Domain Driven Design, and Rust. Use when working on Rust, Cargo, or crate projects, or when the user asks about software architecture, domain modeling, clean architecture, hexagonal architecture, or DDD patterns like aggregates, value objects, entities, and repositories.

2026-05-021

name	git-conventions
description	Git command rules, commit message conventions, and safe usage patterns. Use when the user asks to commit, create a branch, check differences, write a commit message, or perform any git operation. Also use when discussing version control workflows or git safety.

Git Conventions

When to use

User asks to commit, stage, diff, or perform any git operation
User asks to create a branch or write a commit message
User asks to check differences with a previous version
User mentions "git", "commit", "branch", "diff", or "version control"
User is ready to commit after completing a task

Overview

Rules for safe and consistent git usage.

Rules

Before committing, the code must compile and tests must be successful without failing / ignored tests.

Command rules

Never use the command push.
Never use the option force --force.
Never amend commit to modify files, prefer adding more commits (fix commit) and explain the error/reason.
Before running a new git command, ask to add it in the allow list.
Do not hesitate to use git when checking differences with the previous version.
A task should be committed when tests pass (with assertions) and code coverage is verified.

Commit message

A git commit message must start with:

feat: for feature
fix: when fixing the codebase
refac: for refactoring, mostly to prepare or finish a feat
chore: to cleanup the codebase, removing dead code
doc: when touching to .md files or documentation
test: when touching test only