Skill

commit

Use when committing changes to git — provides commit message formatting rules and an interactive commit workflow.

npx claudepluginhub lachtan/nicecode --plugin core

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Commit message formatting rules and an interactive commit workflow.

SKILL.md

Similar Skills

commit

Stages intended Git changes, avoiding secrets, and commits with clear Conventional Commit messages. Use when work is ready and diff is understood.

blueprint

git-commit

Creates git commits with clear, value-communicating messages from staged or unstaged changes, following repo conventions or conventional commit format. Use when user says 'commit' or 'save changes'.

spec-first

git-commit-helper

Generates descriptive commit messages following conventional commits format by analyzing git diffs. Useful when writing commit messages or reviewing staged changes.

2 files

developer

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMar 26, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Git Commit

Commit message formatting rules and an interactive commit workflow.

Formatting Rules

Language: Choose based on context of existing commits. If unclear, ask the user.

Subject line: first line, max ~100 characters. Concisely describes the essence of the change — choose whether to emphasize what changed or why, depending on context.

Body: separated from the subject by a blank line, optional. Keep it brief and to the point — only what is not obvious from the diff. Avoid unnecessarily long descriptions.

Free format: do not use prefixes like feat:, docs:, refactor:.

No co-authorship: do not add a Co-Authored-By: ... line to commit messages unless the user explicitly requests it.

Workflow

Run git status — check the state of the working tree and staging area.

If there are unstaged or untracked changes, ask the user whether to add them to staging (git add .).

If there are no staged changes, inform the user and stop.

Show the diff of staged changes for context.

Based on the diff, propose a commit message following the formatting rules above.

Show the proposed commit message to the user for approval.

After approval, run git commit.

Git Commit

Commit message formatting rules and an interactive commit workflow.

Formatting Rules

Language: Choose based on context of existing commits. If unclear, ask the user.
Subject line: first line, max ~100 characters. Concisely describes the essence of the change — choose whether to emphasize what changed or why, depending on context.
Body: separated from the subject by a blank line, optional. Keep it brief and to the point — only what is not obvious from the diff. Avoid unnecessarily long descriptions.
Free format: do not use prefixes like feat:, docs:, refactor:.
No co-authorship: do not add a Co-Authored-By: ... line to commit messages unless the user explicitly requests it.

Workflow

Run git status — check the state of the working tree and staging area.
If there are unstaged or untracked changes, ask the user whether to add them to staging (git add .).
If there are no staged changes, inform the user and stop.
Show the diff of staged changes for context.
Based on the diff, propose a commit message following the formatting rules above.
Show the proposed commit message to the user for approval.
After approval, run git commit.