agentleFS
Sign inStart free
RileyCorneliusRileyCornelius/Code-Skills/skills/git-commit/SKILL.md

git-commit

Skill0 starsChanged 7 months agoMITView on GitHub

Generate well-structured git commit messages with a standard subject line and optional description. Use when committing staged changes, writing commit messages, or when the user asks to commit.

174 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use git-pr, github-pr-create and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • klauswgSkill

    git-pr

    Prepare, review, publish, or update a complete GitHub pull request for the current repository, including local commit readiness, safe push strategy, semantic title validation, repository-native PR templates, issue linking, and checks verification. Use when the user asks to draft, create, submit, publish, open, or update a pull request. Always require the user to review and explicitly approve the exact final PR before any push or GitHub write.

    Also in 11 projects that use this

  • mjun0812Skill

    github-pr-create

    Pull Requestを作成するSkill。現在のbranchからpull requestを作成する。言語指定可能。 ユーザーが「PR作って」「pull request作成して」のように依頼したら使うこと。

    Also in 3 projects that use this

  • MicrosoftSkill

    git-branch

    Branch management for implementation. Use when you need to create a branch, switch branches, checkout, or verify branching strategy before implementing code. Do not use for commits (use git-commit), pull requests (use pull-request), or advanced git operations (rebase, merge).

    Also in 4 projects that use this

  • klauswgSkill

    git-issue

    Prepare, review, create, or update evidence-based GitHub issues for the current repository with duplicate detection, repository-native templates, valid labels, and post-publication verification. Use when the user asks to draft, file, submit, publish, edit, or refine a GitHub issue, bug report, feature request, performance issue, or technical proposal. Always require the user to review and explicitly approve the exact final issue before any GitHub write.

    Also in 3 projects that use this

  • gologo13Skill

    git-push

    Push current branch to origin and sync with remote updates; keywords: git, rebase. Use only on explicit request; before execution, review diffs and list impact scope.

    Also in 6 projects that use this

  • GoogleSkill

    github-pr-review

    Review a GitHub pull request and leave inline comments in a natural human reviewing voice, indistinguishable from comments typed by hand on the GitHub web UI. Deliberately bounded to defects a reader can settle by looking at the anchored line, rather than a deep audit, so every comment is cheap for the author to check. Scales to 2-20 comments by PR size, parallelises analysis across sub-agents, drafts for approval, then posts individually with human pacing. Use when the user says "review this PR", "review PR 123", pastes a github.com/.../pull/N link, or asks for comments on a pull request. Don't use for reviewing local uncommitted changes or a diff against a branch (use the `review` skill for that).

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 134 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Commit messages must have a subject line and may have a description.

    line 10
  2. Distinctive:

    Add | Create a capability e.g.

    line 20
  3. Distinctive:

    Remove | Remove a capability e.g.

    line 21
  4. Distinctive:

    Update | Update a capability e.g.

    line 22
  5. Distinctive:

    Start | Begin doing something.

    line 26
  6. Distinctive:

    Do not assume the reader understands what the original problem was.

    line 37
  7. Distinctive:

    Update getting started documentation

    line 48

“Common” is measured: kept by at least 6 in 10 of the 134 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Git Commit

General Rules

  • Commit messages must have a subject line and may have a description.
  • The subject line should start with Standard Terminology.
  • The subject line should be capitalized and must not end in a period.
  • The subject line should be written in imperative mood (Fix, not Fixed / Fixes etc.).
  • The description should only contain explanations as to what and why, never how. The latter belongs in documentation and implementation.

Standard Terminology

First WordMeaning
AddCreate a capability e.g. feature, class, dependency.
RemoveRemove a capability e.g. feature, class, dependency.
UpdateUpdate a capability e.g. feature, class, dependency.
FixFix an issue e.g. bug, typo, accident, misstatement.
RefactorA change that just refactors existing code.
OptimizeRefactor of performance, e.g. speed up code.
StartBegin doing something; e.g. create a feature flag.
BumpRelease a version must contain a version number.

Description

Use the description to explain the background and reasoning, not the implementation. You can save all fellow developers and your future self some time by explaining why you did what instead of how you did it. Only use a description when the reasoning is not obvious. If the reasoning is obvious, skip the description and just write a clear subject line.

  • Describe why a change is being made.
  • How does it address the issue?
  • What effects does it have?
  • Describe any limitations of the current code.
  • Do not assume the reader understands what the original problem was.
  • Bullet points are okay.
  • Descriptions are not always necessary.

Examples

In keeping with the standard output of git itself, all commit subject lines must be written in imperative mood.

Good

  • Add feature X
  • Refactor X for readability
  • Update getting started documentation
  • Remove deprecated methods
  • Bump v1.0.0

Bad

  • Fixed bug with Y
  • Changing behavior of X

Ugly

  • More fixes for broken stuff
  • Sweet new API methods
  • 42

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free