commitlisted

Create a git commit following the Conventional Commits specification (conventionalcommits.org). Reads the diff, auto-infers scope from file paths, proposes type + scope + description + body, and shows the message for approval before committing. Supports optional push, language choice, Codex attribution, staging control, breaking-change marking, amend, and issue references. Global and project-agnostic. Trigger when the user says "commit", "make a commit", "commit my changes", "create a commit", "$commit", or "commit with conventional commits".
ada-ggf25/AI-Tools · ★ 2 · Code & Development · score 66

Install: claude install-skill ada-ggf25/AI-Tools

# Conventional Commits — git commit skill Creates a well-formed [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) commit from the current working tree. Reads the diff, proposes a message for approval, then commits. Never commits silently — the user always sees and approves the message first. ## Accepted flags (parsed from the user's invocation text) | Flag | Effect | |---|---| | `--push` | `git push` after a successful commit | | `--british` | British English spelling in the message (default: American English) | | `--credit` | Append a Codex co-author trailer to the commit | | `--all` | Stage all modified/deleted tracked files before committing (equivalent to `git add -u`) | | `--staged` | Commit only what is already staged; never touch the index | | `--breaking` | Mark as a breaking change (appends `!` and adds `BREAKING CHANGE:` footer) | | `--amend` | Amend the last commit instead of creating a new one | | `--closes N` | Append `Closes #N` footer | | `--refs N` | Append `Refs #N` footer | If the user provides a free-text hint (e.g. `$commit fix the login redirect loop`), use it as a strong signal for the description — do not ignore it. ## Conventional Commits format ```text <type>[optional scope]: <description> <body> [optional footers] ``` **Types:** `feat`, `fix`, `docs`, `style`, `refactor`, `perf`, `test`, `build`, `ci`, `chore` **Scope:** noun in parentheses describing the section of the codebase (e.g. `feat(auth):`) **Breaking change