git-commits

Enforce single-line Git commit messages without Co-Authored-By trailers.

Updated Mar 6, 2026

Search Tags:#git #developer tools #code review #version control #commit

Ready to run

npx skills add https://github.com/ryan-ressmeyer/llm-skills --skill git-commits-ryan-ressmeyer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-commits
Source: https://github.com/ryan-ressmeyer/llm-skills/tree/main/git-commits
Command: npx skills add https://github.com/ryan-ressmeyer/llm-skills --skill git-commits-ryan-ressmeyer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces a strict convention for Git commit messages, ensuring clarity and scannability of your project's history.

Core Features & Use Cases

Single-Line Commits: Enforces that all commit messages are on a single line, preventing multi-line messages and bodies.
No Co-Authored-By: Automatically omits any Co-Authored-By trailers.
Use Case: When you're about to commit a change, use this skill to ensure your message is brief and adheres to the single-line rule, making git log --oneline perfectly readable.

Quick Start

Use the git-commits skill to format your next commit message.

Frequently Asked Questions about git-commits

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

FAQPage Schema

How do I write single-line git commit messages?▼

Single-line git commit messages are enforced by formatting your message to fit on one line without a body. This keeps your version control history terse and scannable, preventing noise in logs and merge commits.

Why should I omit Co-Authored-By trailers in git commits?▼

Omitting Co-Authored-By trailers prevents noise in your version control history. Removing these trailers optimizes commit history for scannability in tools like `git log --oneline` and keeps blame annotations clean.

What is the best way to optimize git log for scannability?▼

The best way to optimize git log scannability is to enforce terse, single-line commit messages. Adhering to this format prevents multi-line messages and ensures `git log --oneline` remains perfectly readable.

Can I use multi-line commit bodies with this formatting approach?▼

No, this approach prohibits multi-line commit bodies to enforce a strict single-line convention. It ensures clarity and scannability by preventing multi-line messages from cluttering your project's history.

Does enforcing single-line commits affect git blame annotations?▼

Yes, enforcing single-line commits positively affects git blame annotations by preventing noise. It adheres to a terse, informative message format that keeps annotations clean and free of clutter from trailers.