agentleFS
Sign inStart free
gologo13gologo13/agent-skills/skills/git-commit/SKILL.md

git-commit

Skill0 starsChanged 9 months agoMITView on GitHub

Create a short, focused commit message and commit staged changes; keywords: git, review, commit, fix. Use only on explicit request; skip in routine implementation discussions.

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 123 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:

    Create a short, focused commit message and commit staged changes.

    line 10
  2. Distinctive:

    Check the diff: git diff --cached (if changes are staged) or git diff (if unstaged)

    line 15
  3. Distinctive:

    Check the branch name for an issue key (Linear, Jira, GitHub issue, etc.)

    line 18
  4. Distinctive:

    If an issue key (e.g., POW-123, PROJ-456, #123) is not already available in the chat or commit context, optionally ask the user if they …

    line 19
  5. Distinctive:

    Imperative mood: Use "fix", "add", "update" (not "fixed", "added", "updated")

    line 36
  6. Distinctive:

    No period: Don't end the subject line with a period

    line 38
  7. Distinctive:

    Describe why: Not just what - "fix stuff" is meaningless

    line 39

“Common” is measured: kept by at least 6 in 10 of the 123 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 Create Commit

Overview

Create a short, focused commit message and commit staged changes.

Steps

  1. Review changes
    • Check the diff: git diff --cached (if changes are staged) or git diff (if unstaged)
    • Understand what changed and why
  2. Ask for issue key (optional)
    • Check the branch name for an issue key (Linear, Jira, GitHub issue, etc.)
    • If an issue key (e.g., POW-123, PROJ-456, #123) is not already available in the chat or commit context, optionally ask the user if they want to include one
    • This is optional - commits can be made without an issue key
  3. Stage changes (if not already staged)
    • git add -A
  4. Create short commit message
    • Base the message on the actual changes in the diff
    • Example: git commit -m "fix(auth): handle expired token refresh"
    • Example with issue key: git commit -m "PROJ-123: fix(auth): handle expired token refresh"

Template

  • git commit -m "<type>(<scope>): <short summary>"
  • With issue key: git commit -m "<issue-key>: <type>(<scope>): <short summary>"

Rules

  • Length: <= 72 characters
  • Imperative mood: Use "fix", "add", "update" (not "fixed", "added", "updated")
  • Capitalize: First letter of summary should be capitalized
  • No period: Don't end the subject line with a period
  • Describe why: Not just what - "fix stuff" is meaningless

Download now (ZIP)

  • Other versions161 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 161

    1. github/awesome-copilot★ 41ksame name
    2. doocs/leetcode★ 37ksame name
    3. tisfeng/Easydict★ 15ksame name
    4. doocs/md★ 13ksame name
    5. spinabot/brigade★ 11ksame name
    6. GitTools/GitVersion★ 3.1ksame name
    7. igorescodro/alkaa★ 1.6ksame name
    8. microsoft/hve-core★ 1.6ksame name
    9. rohaquinlop/complexipy★ 890same name
    10. decebals/claude-code-java★ 763same name

    151 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use git-pr, github-pr-create and 9 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 8 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

    • MicrosoftSkill

      git-merge

      Integrate branches with merge or rebase, resolve conflicts, and execute an ordinary push when explicitly authorized. Use for guided integration with optional conflict-review pauses.

      Also in 3 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

  • In this repository31 other files it gives its agents.

Does it work?

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

Reviews can't be read right now.

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