Git Commit Writer

Writes conventional commit messages by analyzing your staged git changes. Detects commit type, scope, and breaking changes automatically.

Install
cmdop skills install agensi-git-commit-writer

Git Commit Writer is a skill that reads staged git diffs and produces commit messages that follow the Conventional Commits specification. Rather than leaving developers to write freeform messages, it inspects the actual changes in the staging area and determines the appropriate commit type — such as feat, fix, refactor, docs, or chore — based on what was modified. It derives the scope from the changed files, so the output is specific to the code that was actually touched. When a staged diff includes breaking changes, the skill flags them accordingly in the commit message. If multiple logically distinct changes have been staged together, the skill suggests splitting them into separate commits rather than bundling unrelated work into one message. The skill works with any git repository and requires no configuration tied to a specific hosting provider or workflow. This makes it suitable for any project regardless of language, framework, or CI setup. The primary value is replacing vague or inconsistently formatted commit messages with structured, machine-readable entries that other tools — changelogs, semantic versioning scripts, code review systems — can parse reliably.

Use cases

  • Generate a Conventional Commits message from a staged diff before running git commit
  • Detect whether staged changes contain a breaking change that requires a major version bump
  • Identify the correct commit type (feat, fix, refactor, docs, chore) from the diff automatically
  • Derive the scope label from the files changed in the staging area
  • Get a prompt to split mixed staged changes into separate focused commits

When to use it

  • When working in a repository that uses or intends to adopt the Conventional Commits standard
  • When generating changelogs or semantic version numbers from commit history
  • When code review processes depend on readable, consistently formatted commit messages
  • When staging complex diffs that may span multiple logical concerns

When not to use it

  • When the project uses a custom commit message format incompatible with Conventional Commits
  • When no changes are staged, as the skill operates on the staged diff
  • When commit message policy is enforced by a separate tool that must not be bypassed