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

git-commit

Skill1 starsChanged 9 days agoApache-2.0View on GitHub

Generates Conventional Commit messages from selected Git changes. Use when user asks to draft a commit message from current worktree; never stage or 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

  • Other versions174 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 174

    1. github/awesome-copilot★ 41ksame name
    2. doocs/leetcode★ 37ksame name
    3. tisfeng/Easydict★ 15ksame name
    4. doocs/md★ 14ksame name
    5. spinabot/brigade★ 11ksame name
    6. PC2005-cloud/dsh-pet★ 5.9ksame name
    7. GitTools/GitVersion★ 3.1ksame name
    8. igorescodro/alkaa★ 1.6ksame name
    9. microsoft/hve-core★ 1.6ksame name
    10. mattmireles/gemma-tuner-multimodal★ 1.5ksame name

    164 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.

  • In this repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 134 edited versions we read keep these.

  • 4

    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:

    Run git status --short. Read selected diffs with git diff --cached, git diff, and untracked file contents when in scope.

    line 10
  2. Distinctive:

    No changes: report, stop.

    line 12
  3. Distinctive:

    All changes = cached + unstaged diffs + in-scope untracked contents.

    line 17
  4. Distinctive:

    Never run git add, git commit, or commands that change files or index.

    line 25

“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 Message

Workflow

  1. Run git status --short. Read selected diffs with git diff --cached, git diff, and untracked file contents when in scope. Treat untracked files as unstaged. Use no unrelated files, docs, history, branch names, or issue/PR metadata.
  2. Pick scope:
    • No changes: report, stop.
    • Staged only: use cached diff; proceed.
    • Staged + any unstaged/untracked: ask, "Staged only, or all changes (staged + unstaged + untracked)?" Wait.
    • Unstaged only, including only untracked: use all; treat as staged, never stage.
    • Staged-only excludes unstaged edits and untracked files. For partially staged files, use cached diff only; never use working-tree contents.
    • All changes = cached + unstaged diffs + in-scope untracked contents.
  3. Inspect all selected changes. Identify primary change and verified details. Use paths only for optional scope, not behavior. Unresolved conflicts: stop; ask user to resolve. Binary, opaque, or insufficient diffs: ask or report limit; never guess.
  4. Compose:
    • Title: type(scope): imperative summary; scope optional. Choose type from primary change (feat, fix, refactor, perf, test, docs, build, ci, chore, etc.). Keep concise and factual.
    • Body: 2-4 concise bullets on distinct, verified changes. Fewer if warranted; no padding or assumed motives.
    • Footer: only when supported. Verified breaking change: add ! to title and BREAKING CHANGE: .... Issue footer: ID must appear in selected changes.
  5. Output raw message only: title, bullets, optional footer. No preamble, explanation, or code fence.

Never run git add, git commit, or commands that change files or index.

Shape example

Example only; derive actual wording from selected changes.

feat(labels): support bulk updates

- Apply one supplied value across selected labels.
- Preserve unrelated label fields.

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