genshijin-commit

Original：🇨🇳 Chinese

Translated

Generate ultra-compact commit messages. Follows the Conventional Commits format with subject ≤50 characters, prioritizing "why" over "what". Supports both Japanese and English. Trigger with "Make a commit message", "/commit", or "/genshijin-commit". Auto-trigger candidate when staging changes.

2installs

Sourceinterfacex-co-jp/genshijin

Added on2026-04-24

NPX Install

npx skill4agent add interfacex-co-jp/genshijin genshijin-commit

SKILL.md Content (Chinese)

View Translation Comparison →

Commit messages should be concise and accurate. Follow the Conventional Commits format. No redundancy. Prioritize "why" over "what".

Rules

Subject

<type>(<scope>): <imperative summary>

—

<scope>

is optional

types:

feat

,

fix

,

refactor

,

perf

,

docs

,

test

,

chore

,

build

,

ci

,

style

,

revert

Imperative form: Use verbs like "Add", "Fix", "Remove" — do not use past tense (e.g., "Added") or polite/conjugated forms (e.g., "Will add")
Target ≤50 characters, maximum 72 characters
No trailing period
Match the language (Japanese/English) of the repository's existing commit history (check with
```
git log
```
)

Body (only when necessary)

Omit if the subject is self-explanatory
When including:
- Non-obvious "why" behind the change
- Breaking changes
- Migration notes
- Related issues/PRs
Wrap at 72 characters
Use
```
-
```
for bullet points (do not use
```
*
```
)
Reference issues/PRs at the end:
```
Closes #42
```
```
Refs #17
```

Strictly prohibited

Phrases like "This commit will...", "I", "We", "Currently", "Now" — these are self-evident from the diff
"Requested by..." — use the
```
Co-authored-by
```
trailer instead
AI attribution like "Generated with Claude Code"
Emojis (unless required by project conventions)
Repeating filenames already mentioned in the scope

Examples

diff: New endpoint for user profiles, explain the "why" in the body

❌

feat: Add a new endpoint to fetch user profile information from the DB

✅

feat(api): Add GET /users/:id/profile

To reduce LTE bandwidth usage during mobile client cold starts,
a dedicated endpoint is needed to fetch profile data without the full user payload.

Closes #128

diff: Breaking API change

✅

feat(api)!: Rename /v1/orders to /v1/checkout

BREAKING CHANGE: Clients using /v1/orders must migrate to /v1/checkout by June 1, 2026.
After that date, the old route will return 410 Gone.

diff: Small bug fix (example with no body needed)

✅

fix(auth): Fix token expiration check boundary condition

Auto-clarity

The following require a body (subject-only is prohibited):

Breaking changes
Security fixes
Data migrations
Revert commits

Future debuggers will need context. Don't over-compress.

Boundaries

Only generates commit messages. Does not execute
```
git commit
```
, stage changes, or amend commits.
Output is in a format that can be pasted into code blocks.
Disable with commands like "Stop genshijin commits" or "Normal mode"