Individual skill

smart-commit

Create clean Conventional Commits: inspect the diff, group related changes, run quality checks, and write type(scope) messages. Use when committing work, or when the user runs /smart-commit or asks to commit changes.

skills/smart-commit/SKILL.md

Read pinned source

Source commit 8facda86fe36c675a53dc53941e24223c31facaa

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 80
Repository last updated: Oct 21, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

claude-code Repository topic
claude-code-plugin Repository topic
claude-code-plugins Repository topic
claude-code-skills Repository topic
ai-agents Repository topic
ai-coding Repository topic
anthropic Repository topic
automation Repository topic
developer-tools Repository topic
tdd Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 2,873 bytes

Read excerpt


# Smart Commit

Create a high-quality commit for current changes.

## Execution

1. Inventory changes: run `git status` and `git diff` (plus `git diff --staged` for already-staged work) to see everything that changed.
2. Group related changes into logical commits — list the files that belong to each group so one commit maps to one concern.
3. Run available quality gates (test suite, linter, formatter) if the project configures them, and fix failures before committing.
4. Stage each group in turn with `git add <files>`.
5. Craft a Conventional Commits message — `type(scope): description`, with a body that explains why the change was made.
6. Commit the staged group.
7. Confirm the result with `git log --oneline -n` (choose `n` to cover the commits you just made).