1. Habit
  2. Skills
  3. Genshijin Commit skill
interfacex-co-jp · 12K installs

Genshijin Commit skill
Runs by itself, changes are staged.

Short commit messages that explain why.

Install the Genshijin Commit skill and make it a habit: follow https://gethabit.dev/skills/interfacex-co-jp/genshijin-commit.md

  1. 1Copy
  2. 2Paste into Claude Code, Codex or Cursor
  3. 3It runs by itself

12K installs333 starsMIT licenceSource on GitHub ↗

Genshijin Commit

by interfacex-co-jp · 12K installs

The skill

The genshijin commit skill writes very short Conventional Commits messages in Japanese or English, with the reason first and a body only when it adds context.

Only when you ask.

The habit

Short commit messages that explain why.

↻ Runs by itselfchanges are staged

How the habit works.
You don't have to.

Three questionsWhen does it start? How does it check its work? What does it remember?

01

It starts by itself

changes are staged. Runs in Claude Code routine.

  • ↻ changes are staged
  • staged changes or /genshijin-commit

02

It checks its work

subject and body rules. If a check fails, it tries again.

  • ✓subject stays within 72 characters
  • ✓type is one of feat, fix, refactor, perf, docs, test, chore, build, ci, style, revert
  • ✓subject has no trailing period
  • ✓breaking, security, migration and revert commits have a body

03

It remembers

repo commit style. The next run reads it first: the language and scopes the repo uses, taken from git log.

loops/genshijin-commit-loop/style.md

One run, step by step.
Then it stops.

Stop ruleStops after one message per staged change, with at most 2 rewrites.

  1. 01

    Read the history

    The agent checks git log to match the language of earlier commits.

  2. 02

    Read the diff

    It looks at the staged change and picks a type and an optional scope.

  3. 03

    Write the subject

    It writes one imperative summary, aiming for 50 characters, without a period.

  4. 04

    Add a body if needed

    It explains a non-obvious reason, breaking change, migration note or issue reference like Closes #42.

  5. 05

    Check the rules

    Length, type, banned phrases and the required body cases are tested; a failing message is rewritten.

  6. 06

    Hand it over

    The message comes back in a code block, and the style notes get updated.

What it may do.
Nothing more.

Safe by defaultIt writes only in its own folder and asks you before anything goes out.

Is it for you?
Use it when it fits.

Quick checkRead both lists. If the left one sounds like you, the Genshijin Commit skill helps.

Use it when

  • ✓ you have staged changes and need a message
  • ✓ your repo uses Conventional Commits
  • ✓ you want messages that say why, not what

Skip it when

  • – you want the agent to run git commit itself
  • – your team uses a different commit format

Questions

Genshijin Commit skill, answered.

Does it run git commit?

No. It only writes the message. You stage, commit and amend yourself.

Japanese or English?

Both. It follows the language already used in the repo's git log.

How do I turn it off?

Ask for normal mode and it stops the terse style.

How do I install the Genshijin Commit skill?

Copy the prompt at the top into your agent. It installs the skill from interfacex-co-jp/genshijin and sets up the habit. Or run npx skills add interfacex-co-jp/genshijin --skill genshijin-commit.

Is the Genshijin Commit skill free?

Yes. It is published under MIT. Habit is free too.

Genshijin Commit. Now as a habit.

Install the Genshijin Commit skill and make it a habit: follow https://gethabit.dev/skills/interfacex-co-jp/genshijin-commit.md

  • Free
  • No account
  • Undo in one line

All interfacex-co-jp skills →More code skills →

Works in

  • Claude Code
  • Codex
  • Cursor
  • ChatGPT
  • Claude app

Made by interfacex-co-jp, published under MIT. Habit links to the original and never changes it. Is this your skill?

Copying didn't work here. Select the line and copy it by hand.