agentsclimarketplace
Sign in

Commit practices

Skill gdebenedetti/skills/skills/commit-practices

Use when planning, reviewing, or writing git commits. Keep commits atomic and small, use English commit messages, describe concrete functionality, and follow Conventional Commits.From its SKILL.md

Install
npx -y skills add gdebenedetti/skills --skill commit-practices

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.4 KB, 271 tokens by cl100k_base, as published. Nobody here has run it

Commit Practices

Use this skill when preparing a commit or deciding whether a change should be split.

  • One commit, one coherent change that can be reviewed and tested on its own.
  • Split unrelated fixes, refactors, docs, and tests unless the test or doc change belongs directly to the same behavior change.
  • Keep commits small. If the subject needs "and", it is probably two commits.
  • Write commit messages in English.
  • Use the Conventional Commits format: <type>[optional scope]: <description>.
  • Prefer clear types such as feat, fix, docs, refactor, test, chore, build, ci, perf, style, and revert.
  • Write the description as a concise statement of concrete functionality or behavior. Prefer feat(auth): add session timeout warning over wip, more updates, address feedback, or continue work.
  • Use an optional body when the why or the impact is not obvious from the subject alone.
  • Mark breaking changes explicitly with ! after the type or scope, and describe them in a BREAKING CHANGE: footer when relevant.
  • Before committing, check git diff --staged and confirm the staged change matches a single sentence and the chosen type still fits that sentence.

What ships with it: 1 file

187 B alongside SKILL.md

agents/

Gives 2 of the 12 instructions most pr commit review skills give in 271 tokens

Counted across 888 of the 1,342 authors here whose files we hold, read 2026-08-07

  • Use conventional commits formathere, and in 127 of 888, across 115 files
  • Keep subject line under 72 charactersin 62 of 888, across 48 files
  • Delete branches after mergein 51 of 888, across 38 files
  • Use imperative mood in subject linein 51 of 888, across 42 files
  • Use imperative mood in commit messagesin 44 of 888
  • Verify directory is ignored before creating worktreein 43 of 888, across 12 files
  • Generate a conventional commit messagein 43 of 888
  • Add unignored worktree directories to gitignorein 42 of 888, across 10 files
  • Make atomic commitsin 39 of 888, across 27 files
  • Run tests before committingin 36 of 888, across 25 files
  • Verify clean test baselinein 35 of 888, across 9 files
  • Split unrelated changes into separate commitshere, and in 35 of 888, across 30 files

Said here and by no other author read

  • describe concrete functionality in the subject

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,852. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.