Skillibary
Submit

git-commit-writer

verified

Writes clear, conventional git commit messages from staged diffs.

Purpose

Analyzes a git diff and produces a well-structured commit message following the Conventional Commits specification.

Trigger

Use when the user asks to "write a commit message", "commit this", or "summarize my changes".

Behavior

  1. Read the staged diff (git diff --cached).
  2. Identify the primary change type: feat, fix, refactor, docs, test, chore, perf, ci.
  3. Identify the scope (module, package, or file area most affected).
  4. Write a subject line: <type>(<scope>): <imperative summary> — max 72 chars.
  5. Add a body paragraph if the change is non-trivial, explaining why not what.
  6. Add BREAKING CHANGE: footer if any public API changed incompatibly.

Output Format

feat(auth): add OAuth2 PKCE flow for mobile clients

Replace implicit grant with PKCE to comply with RFC 9700.
Drops support for clients that cannot generate a code verifier.

BREAKING CHANGE: /oauth/token no longer accepts implicit grants.

Constraints

  • Subject line must be imperative mood ("add", not "added" or "adds").
  • Never mention file names in the subject unless essential.
  • Do not pad short commits with filler phrases.