agentsclimarketplace
Sign in

Git conventions

Skill itzcull/software-skills/skills/git-conventions

Git commit conventions covering stability invariants, conventional commit types (feat, fix, refactor, test, chore), message formatting (imperative voice, 50/72 rule), TDD commit rhythm (commit after each RED-GREEN-REFACTOR step), and PR standards. Use when writing commit messages, structuring commits, or reviewing git history quality.From its SKILL.md

Install
npx -y skills add itzcull/software-skills --skill git-conventions

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

  • 3 stars3 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.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.5 KB, as published. Nobody here has run it

Purpose

Define the conventions for git commits that maintain a clean, bisectable, and meaningful project history. Every commit represents stable, working software with incremental, focused changes.

When to use

  • Writing commit messages
  • Deciding what to include in a single commit
  • Structuring commits during TDD (when to commit in RED-GREEN-REFACTOR)
  • Reviewing commit history quality
  • Setting up commit conventions for a new project
  • Understanding conventional commit types and their usage

Key principles

  • Stability first - every commit must pass all tests, build, lint, and type check
  • Incremental progress - small, focused changes easy to review, revert, and bisect
  • Imperative voice - describe what the code DOES when applied
  • Semantic clarity - type prefixes indicate the nature of change at a glance
  • TDD rhythm - commit after GREEN, commit after REFACTOR

Reference files

  • Git commit conventions - Complete guide including stability invariants, commit types, message formatting, TDD commit rhythm, and PR standards

Keep looking

Skills are one crate of 627,801. 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.