skills.rest
JoernStoehler
JoernStoehlerCOMMUNITY
Explore all skills by this author →
GitHub

git-conventions

Enforce Git workflow conventions for commits, diffs, and branch reviews.

Updated Feb 6, 2026
Search Tags:#git#workflow#commit#conventions#diff#branch#code-review
One-click install
npx skills add https://github.com/JoernStoehler/msc-math --skill git-conventions-joernstoehler
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-conventions
Source: https://github.com/JoernStoehler/msc-math/tree/main/.claude/skills/git-conventions
Command: npx skills add https://github.com/JoernStoehler/msc-math --skill git-conventions-joernstoehler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishes Git workflow conventions to keep commits, diffs, and reviews consistent across the project.

Core Features & Use Cases

  • Three-dot diffs for code reviews: use git diff main...HEAD to show only changes on the current branch.
  • Explicit base references: state the base explicitly when discussing diffs to avoid confusion.
  • Commit checklist: ensure tests pass, lint warnings are zero, and the working tree is clean before pushing.

Quick Start

Follow these conventions when committing, diffing, and reviewing branches to keep a clean, understandable history.

Frequently Asked Questions about git-conventions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a three-dot diff and when should I use it for Git code reviews?▼

A three-dot diff, such as git diff main...HEAD, shows only the changes on your current branch. Use this Git diff method during code reviews to isolate branch commits from the main base reference.

How do I standardize Git commit workflows across my repository?▼

To standardize Git commit workflows, enforce a commit checklist requiring tests to pass, zero lint warnings, and a clean working tree. Always state your base reference explicitly when discussing diffs.

Why should I specify an explicit base reference when running a Git diff?▼

Specifying an explicit base reference when running a Git diff avoids confusion between local main and origin/main. It ensures developers review the correct branch changes without ambiguous diff outputs.

What should I check before pushing a Git commit to keep a clean working tree?▼

Before pushing a Git commit, verify that all tests pass and lint warnings are zero to keep a clean working tree. This commit checklist prevents unreviewed changes from entering the remote repository history.

Can I use these Git conventions for local main versus origin/main branch comparisons?▼

Yes, these Git conventions apply to daily development tasks involving local main versus origin/main comparisons. By using explicit base references and three-dot diffs, you maintain consistent branch reviews.

Related Skills

Explore More Software Engineering Skills→
dyoshikawadyoshikawa
1

diff-analyze

Analyze git differences and commit history between the current branch and origin main.

Community
Basic
cbleckercblecker
5

creating-pull-request

Automate GitHub pull request creation with branch pushing and PR metadata.

Community
Basic
ToanPV90ToanPV90

ship

Automate a gated pre-merge pipeline that validates code and creates a pull request.

Community
Advanced
eykdeykd

commit

Create git commits following the conventional commit format.

Community
Intermediate