Agent skill · software engineering · aiskillstore
git-commit-writer-free
Generate conventional commit messages from staged git changes. Use when the user asks to write commit message, generate commit, what should my commit say, or after the user runs git add and wants a commit message for staged files.
Why this skill is useful
Adds a specific workflow for generating conventional commit messages based on staged changes, which the AI wouldn't reliably generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Git Commit Writer Generate a conventional commit message from staged changes only. Workflow 1. Run git status --short. 2. Determine whether any files are staged by checking the first status column for anything other than a space or ?. 3. If no files are staged, do not suggest a commit message. Tell the user to stage changes first with git add <files> or git add .. 4. Run git diff --cached --stat to summarize staged file impact. 5. Run git diff --cached to inspect the staged patch. 6. Analyze the staged changes and return one primary commit recommendation in conventional commit format, plus optional alternatives if useful. Use only staged changes. Do not base the commit message on unstaged, untracked, or working-tree-only changes. Required Commands If git diff --cached is empty, the correct response is: Commit Format Use this format: Use type(scope)!: summary when the staged changes introduce a breaking change. Keep the summary under 72 characters when practical. Use imperative mood: add, fix, update, remove, refactor, not added, fixed, or updates. Type Reference feat: Adds or exposes user-facing functionality. fix: Fixes a bug, regression, crash, bad output, broken state, or incorrect behavior. docs: Changes documentation only. style: Changes formatting, whitespace, lint-only style, or visual styling without behavior changes. refactor: Restructures code without intended behavior change. test: Adds or changes tests, fixtures, mocks, or test infrastructure. chore: Changes maintenance files, build config, dependencies, scripts, metadata, or repository housekeeping. When multiple types apply, choose the type that best represents the user-visible reason for the commit. Prefer feat or fix over chore when product behavior changes. Prefer test only when the commit is primarily test work. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/git-commit-writer-free