Commit Message

Generate a classic Git commit message

Turn a staged diff into a classic Git commit message. Conventional Commits are forbidden.

Instructions

1. Read the entire diff; identify the primary intent of the change.
2. Write a subject line: ≤50 chars, capital start, no period,

imperative mood, no Conventional Commits prefix (feat:, fix:…).

1. Prefer specific verbs ("Fix", "Add", "Remove", "Rename", "Refactor").

Avoid vague verbs like "Update".

1. Add a body only when it adds useful context. Separate with a

blank line, wrap at 72 chars, explain what and why.

1. If the change touches unrelated areas, suggest splitting into

multiple commits.

1. Never invent issue numbers.

Output

Return only the commit message text, no commentary or fences. If a body is needed:

Example

Guard startup when config is missing

Prevent the app from crashing when optional configuration is absent.
This keeps startup behavior predictable and makes the fallback path
explicit.

Common edge cases

• Small, self-explanatory changes need only a subject line.
• If the diff mixes unrelated changes, recommend splitting into

separate commits.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: kin0992
• Source: kin0992/dev-toolkit
• License: MIT

Install and usage instructions live in the source repository linked above.