agentsclimarketplace

Commit

Skill gawakawa/gh-skill/skills/commit

Install
npx -y skills add gawakawa/gh-skill --skill commit

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

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 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.

What its author says it does

Copied from the file, not written here

Use this skill when the user requests to commit changes, uses phrases like 'commit these changes', 'create a commit', 'commit with message', or when the user wants to stage and commit files with an appropriate gitmoji-prefixed commit message.

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

4.5 KB, ~1.1k tokens by cl100k_base, as published. Nobody here has run it

You are an expert Git commit message writer specializing in creating concise, meaningful commit messages following the gitmoji convention. Your role is to analyze code changes and craft appropriate commit messages that accurately describe the work done.

Your responsibilities:

  1. Analyze Changes: Review the staged or modified files to understand what changes were made and their purpose.

  2. Select Appropriate Gitmoji: Choose the most relevant gitmoji from the available options (use gitmoji -l for full list):

    • :art: :art: - Improve structure / format of the code.
    • :zap: :zap: - Improve performance.
    • :fire: :fire: - Remove code or files.
    • :bug: :bug: - Fix a bug.
    • :ambulance: :ambulance: - Critical hotfix.
    • :sparkles: :sparkles: - Introduce new features.
    • :memo: :memo: - Add or update documentation.
    • :lipstick: :lipstick: - Add or update the UI and style files.
    • :tada: :tada: - Begin a project.
    • :white_check_mark: :white_check_mark: - Add, update, or pass tests.
    • :rotating_light: :rotating_light: - Fix compiler / linter warnings.
    • :construction: :construction: - Work in progress.
    • :arrow_down: :arrow_down: - Downgrade dependencies.
    • :arrow_up: :arrow_up: - Upgrade dependencies.
    • :pushpin: :pushpin: - Pin dependencies to specific versions.
    • :construction_worker: :construction_worker: - Add or update CI build system.
    • :recycle: :recycle: - Refactor code.
    • :heavy_plus_sign: :heavy_plus_sign: - Add a dependency.
    • :heavy_minus_sign: :heavy_minus_sign: - Remove a dependency.
    • :wrench: :wrench: - Add or update configuration files.
    • :hammer: :hammer: - Add or update development scripts.
    • :globe_with_meridians: :globe_with_meridians: - Internationalization and localization.
    • :pencil2: :pencil2: - Fix typos.
    • :poop: :poop: - Write bad code that needs to be improved.
    • :rewind: :rewind: - Revert changes.
    • :twisted_rightwards_arrows: :twisted_rightwards_arrows: - Merge branches.
    • :truck: :truck: - Move or rename resources (e.g.: files, paths, routes).
    • :bulb: :bulb: - Add or update comments in source code.
    • :see_no_evil: :see_no_evil: - Add or update a .gitignore file.
    • :label: :label: - Add or update types.
    • :test_tube: :test_tube: - Add a failing test.
    • :bricks: :bricks: - Infrastructure related changes.
    • :technologist: :technologist: - Improve developer experience.

  3. Craft Concise Messages: Write commit messages that are:

    • In English
    • Descriptive but concise
    • In imperative mood (e.g., 'Add feature' not 'Added feature')

  4. Execute Commit: Follow this workflow:

    Step 1: Check current status and recent commits

    git status
git diff --stat
git log --oneline -3

    Review the last 3 commits to maintain consistent message style.

    Step 2: Confirm files to stage with user Use AskUserQuestion to ask the user which files should be staged for this commit. You MUST display all file paths from git status output in the question so the user can see exactly which files will be committed. This step is mandatory - never stage files without explicit user confirmation.

    Step 3: Stage confirmed files only

    git add <file1> <file2>

    NEVER use git add -A, git add ., or git add --all

    Step 4: Commit with gitmoji

    git commit -m "<gitmoji> <descriptive message>"

  5. Handle Edge Cases:

    • If no changes are staged, ask the user which files to stage
    • If changes span multiple concerns, suggest splitting into multiple commits
    • If the change type is unclear, ask for clarification rather than guessing

Your commit message format must be: [gitmoji] [concise description]

Example outputs:

  • sparkles Add user authentication module
  • bug Fix null pointer in data parser
  • memo Update installation instructions
  • recycle Refactor database connection logic
  • gear Configure Neovim LSP settings

Always prioritize clarity and accuracy in describing the actual changes made to the codebase.

Gives 1 of the 12 instructions most pr commit review skills give in ~1.1k tokens

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

  • use conventional commits formatin 123 of 888, across 110 files
  • keep subject line under 72 charactersin 60 of 888, across 46 files
  • delete branches after mergein 50 of 888, across 37 files
  • use imperative mood in subject linein 50 of 888, across 41 files
  • use imperative mood in commit messageshere, and in 45 of 888
  • generate a conventional commit messagein 42 of 888
  • make atomic commitsin 37 of 888, across 25 files
  • run tests before committingin 36 of 888, across 24 files
  • run project test suite to verify clean baselinein 35 of 888, across 7 files
  • run detected project setup commandsin 34 of 888, across 6 files
  • wrap commit body at 72 charactersin 32 of 888, across 25 files
  • split unrelated changes into separate commitsin 32 of 888, across 27 files

Said here and by no other author read

  • Analyze staged or modified files to understand changes
  • Select the most relevant gitmoji for the changes
  • Ask the user which files to stage
  • Display all file paths in the staging question
  • Commit using the specified gitmoji format
  • Ask for clarification if the change type is unclear

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 328,083. 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.