Git commit format

Skill somnio-software/somnio-ai-tools/skills/git-commit-format

Generates properly formatted Git commit messages (title + description) following Conventional Commits. Use this skill whenever the user wants to write a commit message, document code changes in git format, or asks things like "how should I commit this?", "write a commit for these changes", "help me with my commit message", or describes what they changed and needs a git-ready output. Always use this skill when the user describes code changes and needs a commit, even if they don't explicitly say "commit".From its SKILL.md

Install

npx -y skills add somnio-software/somnio-ai-tools --skill git-commit-format

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

One thing to look at

4 stars4 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.

SKILL.md

3.0 KB, as published. Nobody here has run it

Git Commit Format Skill

Generates a commit message (title + description) from a description of changes.

Conventions

Commit Title

Follows Conventional Commits spec:

{type}({optional scope}): {short imperative description}

Types: feat, fix, chore, refactor, docs, style, test, perf, ci, build, revert
Use imperative mood: "add", "fix", "remove" — not "added", "fixed", "removed"
Max ~72 characters
All lowercase except proper nouns
No period at the end
Example: feat(auth): add biometric login support

Commit Description

Bullet list using past tense action words:

* Fixed ...
* Added ...
* Changed ...
* Removed ...

Only include bullets that apply to the actual changes
Keep each bullet concise and specific
Allowed verbs: Fixed, Added, Changed, Removed, Updated, Refactored, Migrated, Deprecated
Always in English
Never include Co-Authored-By, Signed-off-by, or any trailer attributing the commit to an AI agent or tool

Type Selection Guide

Type	When to use
`feat`	New functionality
`fix`	Bug fix
`refactor`	Code change with no behavior change
`chore`	Config, deps, tooling, maintenance
`test`	Adding or updating tests
`docs`	Documentation only
`style`	Formatting, whitespace
`perf`	Performance improvement
`ci`	CI/CD changes
`build`	Build system changes
`revert`	Reverting a previous commit

If the changes span multiple concerns, suggest splitting into separate commits.

Output Format

feat(flutter): upgrade Flutter SDK to v3.19

* Updated Flutter SDK version to 3.19
* Changed minimum iOS deployment target to 14.0
* Fixed deprecated API usages after upgrade
* Removed unused legacy plugins

The commit message must end after the bullet list. Do not append any Co-Authored-By, Signed-off-by, or AI attribution trailers.

Examples

User: "I upgraded Flutter and had to fix some deprecated APIs and update the iOS target"

feat(flutter): upgrade Flutter SDK to v3.19

* Updated Flutter SDK version to 3.19
* Changed minimum iOS deployment target to 14.0
* Fixed deprecated API usages after upgrade

User: "Fixed a crash on login when the user has no internet"

fix(auth): handle login crash when offline

* Fixed crash on login screen when no internet connection is available
* Added offline error state to login flow