Most commit history isn’t written for the moment it’s committed — it’s written for the person debugging a regression eight months from now with no memory of this conversation. This skill gives the agent a consistent way to write that history: which conventional commit type actually applies, when a body paragraph is required versus when a one-line subject is enough, and how to split a tangled diff into commits that could each be reverted on their own.

It also covers the other half of the workflow most agents get wrong — pull request descriptions that either say nothing (“various fixes”) or say everything in unreadable detail. The included template scales from a one-line summary for a trivial fix up to a full Summary / Changes / Testing / Notes breakdown for anything a reviewer actually needs to think about.

Install it once and every commit message, branch name, and PR description in the project starts following the same conventions — without you having to repeat the house style in every session.

When it triggers

committing a change
drafting a PR description
naming a branch
splitting a large diff into commits

Git Commits & Pull Requests

When it triggers