git-conventional-commitslisted

Builds a Conventional Commits commit message for the current changes in git. Analyzes the staged diff (or unstaged, if staged is empty), determines type/scope, writes the subject and, if needed, a body. Use when the user wants to "make a commit", "commit the changes", "commit this", "write a commit message", "commit following the convention".
alexeyshishin/as-skill · ★ 4 · Code & Development · score 73

Install: claude install-skill alexeyshishin/as-skill

# git-conventional-commits — Conventional Commit message for the current diff Goal: instead of the user writing the commit message themselves, you analyze the diff and build a message following the convention in `~/.claude/rules/git-conventions.md`. Before starting, read `~/.claude/rules/git-conventions.md` — it has the full list of allowed `type` values, the scope format, and the principles. ## Step 1. Gather context Run: - `git status --short` — see what's changed - `git diff --staged` (if there's staged content) or `git diff` (if not) — the content of the changes - `git log --oneline -10` — the style of previous commits in the project (especially the language: Russian/English) If staged is empty and unstaged is also empty — tell the user and stop. ## Step 2. Determine the type Read the diff and decide: | diff shows | type | |----------------|------| | a new file with functionality, a new endpoint, a new feature | `feat` | | a logic fix so a bug no longer reproduces | `fix` | | move/rename/simplify with no behavior change | `refactor` | | performance improvement only | `perf` | | only `.md`, code comments | `docs` | | only tests added or fixed | `test` | | `package.json`, `go.mod`, `requirements.txt`, Dockerfile, CI configs | `build` or `ci` | | dependencies, tooling versions | `chore(deps)` | | revert of a previous commit | `revert` | If the diff is mixed (e.g. both `fix` and `refactor`) — **stop and suggest the user split it into several commits**. Don't write "f