# 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. - Skill: `claude-world-director-mode-lite/smart-commit` (Agent Skill) - Install (CLI): `npx skillmds@latest add claude-world-director-mode-lite/smart-commit` - Raw SKILL.md: https://api.skillmd.com/api/skills/claude-world-director-mode-lite/smart-commit/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: claude-world (https://skillmd.com/u/claude-world-director-mode-lite) - Updated: 2026-09-10 - Page: https://skillmd.com/skills/claude-world-director-mode-lite/smart-commit --- # 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 `. 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). Repeat steps 4-6 for each group so unrelated changes land in separate commits. The format and type reference below is your guide for steps 5-6. ## Pre-Commit Checklist ### Scope Check - [ ] Solves one problem only - [ ] No unrelated changes - [ ] No debug code - [ ] No temporary files ### Quality Check - [ ] All tests pass - [ ] Code is formatted - [ ] No linting errors - [ ] Documentation updated --- ## Commit Message Format ``` ():