Agent skill

Commit

by haru in haru/redmine_ai_helper

Stage the current changes and create a git commit with a properly formatted English message.

MITAuto-check: notesDevelopment

Install Commit

skills CLI
$ npx skills add haru/redmine_ai_helper --skill commit -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install haru/redmine_ai_helper commit --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/haru/redmine_ai_helper.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/commit .claude/skills/commit && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
commit
GitHub stars
106
Token cost
~1.1k tokens
SKILL.md length
507 words
Files
1
Skills in repo
21
Repo updated
First seen
Licence
MIT

At a glance

Stage the current changes and create a git commit with a properly formatted English message.

  • Works in 6 steps: Survey the Changes → Stage the Changes → Determine the Commit Type → …
  • The user asks to commit
  • SKILL.md covers User Input, Procedure, Notes and Error Handling
  • Calls git

What it does

Commit is an agent skill from haru/redmine_ai_helper. Stage the current changes and create a git commit with a properly formatted English message. Use whenever the user asks to commit, save, or check in their work. Picks a Conventional-Commits-style prefix (fix:, feat:, refactor:, docs:, test:, chore:, style:, perf:) based on the actual diff, keeps the first line a concise summary, and adds a bullet list of details only when the change touches several things.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Commit messages. It works with Git. The repository describes itself as: A Redmine plugin that adds AI agents, MCP Server, smart completion, and vector search. The licence is MIT.

When your agent uses it

  • The user asks to commit
  • Check in their work

Example prompts

  • “/commit”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Survey the Changes
  2. Stage the Changes
  3. Determine the Commit Type
  4. Write the Commit Message
  5. Commit
  6. Confirm

What it can do on your machine

Read from SKILL.md and the folder at commit 3cd87d6. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Commit loads about 1.1k tokens when it runs. Until then it costs about 104 tokens; SKILL.md has 507 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~104
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:35
    hing looks like a secret or credential (`.env`, `*.pem`, `credentials.json`, API keys, etc.), unstage it and warn the us

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from haru/redmine_ai_helper at commit 3cd87d6, republished under its MIT licence (© haru). 507 words, ~1,093 tokens.

Download SKILL.mdSave it as .claude/skills/commit/SKILL.md (or your agent's skills folder).
name
commit
description
Stage the current changes and create a git commit with a properly formatted English message. Use whenever the user asks to commit, save, or check in their work. Picks a Conventional-Commits-style prefix (fix:, feat:, refactor:, docs:, test:, chore:, style:, perf:) based on the actual diff, keeps the first line a concise summary, and adds a bullet list of details only when the change touches several things.
argument-hint
Optional: additional context about what changed, or which files to include
user-invocable
true
disable-model-invocation
false

Commit

Stage the outstanding changes and create a single git commit with an English message that follows this project's format.

User Input

text
$ARGUMENTS

Consider any additional context from the user input (e.g. "only commit the tool changes", "this is a bug fix") before proceeding.

Procedure

Step 1: Survey the Changes

Run in parallel:

  • git status — see tracked and untracked files
  • git diff and git diff --staged — see the actual content changes
  • git log --oneline -10 — match the repository's existing commit message tone
Step 2: Stage the Changes

Stage the modified and new files that belong to this piece of work (git add <files>, or git add -A when everything in the working tree is part of the same change).

Before committing, look at the staged file list once more:

  • If anything looks like a secret or credential (.env, *.pem, credentials.json, API keys, etc.), unstage it and warn the user instead of committing it silently.
  • If some staged files clearly belong to unrelated, separate work (not what the user is asking to commit right now), leave them out and mention it to the user.
Step 3: Determine the Commit Type

Look at the diff and classify the change into a prefix:

PrefixWhen to use
fix:Bug fix
feat:New feature or capability
refactor:Restructuring without behavior change
docs:Documentation only (README, YARD, locale text)
test:Test-only changes
chore:Tooling, dependencies, config, housekeeping
style:Formatting/whitespace only, no logic change
perf:Performance improvement

If a change spans multiple categories, pick the one that reflects the primary intent.

Show full SKILL.md (253 more words)Show less
Step 4: Write the Commit Message

Format:

  • Line 1: <prefix>: <concise summary of the overall change> — English, imperative mood, no trailing period.
  • If the change is small (one focused fix, a single file, a short diff): stop at line 1. No body needed.
  • If the change touches several things: leave a blank line after line 1, then a short bullet list (- ...), one line per notable change. Keep bullets brief — what changed, not how.

Example (small change):

fix: correct nil check in issue summary cache lookup

Example (larger change):

feat: add vector model profile support to settings

- add use_vector_model_profile and vector_model_profile_id columns
- update settings UI to select a dedicated vector model profile
- fall back to the default model profile when unset

Do not add a Co-Authored-By line or any other reference to Claude/AI assistance — this project's convention explicitly excludes that from commit messages.

Step 5: Commit

Use a heredoc so multi-line messages are formatted correctly:

bash
git commit -m "$(cat <<'EOF'
<prefix>: <summary>

- <detail 1>
- <detail 2>
EOF
)"

Always create a new commit — never --amend an existing one unless the user explicitly asks for it.

Step 6: Confirm

Run git status after the commit and report the resulting commit (short hash + first line) to the user. Do not push.

Notes

  • Never push — this skill only commits locally.
  • Never use --no-verify to skip hooks.
  • Write commit messages in plain English regardless of the conversation language.

Error Handling

  • If there is nothing staged and nothing to stage (clean working tree), tell the user there is nothing to commit — do not create an empty commit.
  • If a pre-commit hook fails, fix the underlying issue, re-stage, and create a new commit — do not amend the previous one (the failed commit never happened).
  • If secrets or clearly unrelated files are detected among the changes, stop and confirm with the user before including them.

© haru, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/commit of haru/redmine_ai_helper.

Open the folder on GitHubat commit 3cd87d6

Compare with similar skills

Commit next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Commit compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Commit this skillharu/redmine_ai_helper106—~1.1kAutomated safety check: NotesMIT
React Router Release Notes Prepremix-run/react-router57k—~1.1kAutomated safety check: PassMIT
ToolJet Multi-Repo CommitToolJet/ToolJet41k—~1.3kAutomated safety check: PassAGPL-3.0
Git Workflow and Versioningaddyosmani/agent-skills103k2 repos~3.5kAutomated safety check: NotesMIT
React Router Pull Request Creatorremix-run/react-router57k—~2.5kAutomated safety check: PassMIT
Verdaccio Pull Request Workflowverdaccio/verdaccio18k—~1.9kAutomated safety check: PassMIT

Similar skills

  • React Router Release Notes Prep

    remix-run/react-router

    Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.

    57k GitHub stars~1.1k tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Commits changes across ToolJet's root repo and its server/ee and frontend/ee submodules, writing messages from the diffs and updating submodule pointers in order.

    41k GitHub stars~1.3k tokensUpdated today
    DevelopmentAuto-check passed
  • Git Workflow and Versioning

    addyosmani/agent-skills

    Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.

    103k GitHub starsUsed in 2 repos~3.5k tokens
    DevelopmentAuto-check: notes
  • React Router Pull Request Creator

    remix-run/react-router

    Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.

    57k GitHub stars~2.5k tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.

    18k GitHub stars~1.9k tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Commits changes in the Saleor codebase and works through pre-commit hook failures from ruff, mypy, the GraphQL schema check and the migrations check.

    23k GitHub stars~575 tokensUpdated yesterday
    DevelopmentAuto-check passed

More from haru/redmine_ai_helper

All 21 skills in this repo
  • Create Pull Request

    haru/redmine_ai_helper

    Create a pull request from the current branch. An agent skill from haru/redmine_ai_helper.

    106 GitHub stars~1.5k tokensUpdated today
    Auto-check passed
  • Create Release Branch

    haru/redmine_ai_helper

    Create a release branch for a given version. An agent skill from haru/redmine_ai_helper.

    106 GitHub stars~599 tokensUpdated today
    Auto-check passed
  • Qlty Check

    haru/redmine_ai_helper

    Code quality checks, formatting, and metrics via qlty CLI. An agent skill from haru/redmine_ai_helper.

    106 GitHub starsUsed in 2 repos~628 tokens
    Auto-check passed
  • Redmine Playwright Login

    haru/redmine_ai_helper

    Connect to the running Redmine instance and log in via the Playwright MCP browser, using REDMINEPLAYRIGHTURL/REDMINEPLAYRIGHTUSER/REDMINEPLAYRIGHTPASSWORD environment variables.

    106 GitHub stars~796 tokensUpdated today
    Auto-check passed
  • Recreate Test DB

    haru/redmine_ai_helper

    Recreate the Redmine test database from scratch (delete db/schema.rb and db/redmine.sqlite3test, then run core and plugin migrations with RAILSENV=test).

    106 GitHub stars~364 tokensUpdated today
    Auto-check passed
  • Create Release Notes

    haru/redmine_ai_helper

    Generate Redmine.org release notes from a GitHub release tag.

    106 GitHub stars~768 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Commit

What does Commit do?

Stage the current changes and create a git commit with a properly formatted English message. Commit is an agent skill from haru/redmine_ai_helper. Stage the current changes and create a git commit with a properly formatted English message.

When should I use Commit?

Commit fits situations like: the user asks to commit; check in their work.

How do I install Commit in Claude Code?

Run `npx skills add haru/redmine_ai_helper --skill commit -a claude-code`. Or copy the skill folder (.claude/skills/commit in haru/redmine_ai_helper) into .claude/skills/commit in your project. Claude Code loads it when a task matches its description.

How do I install Commit in Codex?

Run `npx skills add haru/redmine_ai_helper --skill commit -a codex`. Or copy the skill folder (.claude/skills/commit in haru/redmine_ai_helper) into .agents/skills/commit in your project. Codex loads it when a task matches its description.

Can I use Commit in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add haru/redmine_ai_helper --skill commit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/commit, .gemini/skills/commit, .github/skills/commit and .opencode/skills/commit in your project.

What does Commit need to run?

Going by SKILL.md and its folder, Commit needs the command-line tools its instructions call (git).

Does Commit access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Commit safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Commit use?

Commit is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Commit use?

About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Commit?

Skills that share tags, products or a category with Commit: React Router Release Notes Prep (remix-run/react-router, 57k stars), ToolJet Multi-Repo Commit (ToolJet/ToolJet, 41k stars), Git Workflow and Versioning (addyosmani/agent-skills, 103k stars) and React Router Pull Request Creator (remix-run/react-router, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Commit?

haru (a GitHub user) maintains it in haru/redmine_ai_helper, which has 106 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 8, 2026.

Source: haru/redmine_ai_helper on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.