commit

Writes and validates git commit subject lines, bodies, and trailer lines against repository rules.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/Bascht74/videopodcast-magic --skill commit-bascht74
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/Bascht74/videopodcast-magic/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/Bascht74/videopodcast-magic --skill commit-bascht74

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Commit subjects are read in a list without the diff beside them, and subjects written from the author's inside view fail readers scanning git log --oneline. This Skill enforces five subject-line rules, a changelog probe, body content rules, mandatory trailer lines, and a pre-commit checklist so the log stays a usable source. ## Core Features & Use Cases - Subject line rules: Name the thing by the name users meet it under, state what is different afterwards, give the fix not only the fault, avoid images that need the diff, and keep one commit to one thing verified with git diff --stat. - Body and trailer enforcement: Bodies carry the reason and measured numbers in plain words, and every message ends with the Co-Authored-By and Claude-Session lines, checked by a shell loop over origin/main..HEAD. - Worked case book: Ten real subjects from the repository, bad and good, with what would have carried instead, live in examples.md for consultation when a subject will not come. - Use Case: Before committing a change that touched tests and a workflow file, run the 13-point checklist to split it into two commits and write subjects a stranger can place without the diff. ## Quick Start Use the commit skill to write the commit message for my staged changes and check it against the subject-line rules.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I write a good git commit subject line?▼

Name the thing by the name users meet it under, such as a switch, button, file, or test, and say what is different afterwards rather than what the work was. Apply the changelog probe: if the line would teach a stranger nothing under a Fixed heading, it is too vague.

How to split a commit that is too large?▼

Run git diff --stat and check whether the files fall into groups that could have gone out separately. If they could, make two commits. A subject needing an "and" is a symptom, but the diff stat is the reliable check.

What belongs in a git commit message body?▼

Plain words giving the reason the subject cannot carry, measured numbers, and where the fix deliberately does not reach. Exclude dates, names, file lists, and the story of the day, since git already records metadata and git show --stat prints files.

When should a commit not be made?▼

Only commit when it was asked for; finishing work or a green test suite is not a request. Never commit on the main branch, and never push or tag unless that was explicitly asked for too.

How do I verify commit trailer lines before pushing?▼

Run git log -1 --format=%B | tail -2 to confirm both trailer lines in order, then loop over origin/main..HEAD checking each message for Co-Authored-By and Claude-Session. Amend any commit the loop names before making the next one.