git-commit-writer

# Git Commit Writer ## What this skill does This skill directs the agent to read a git diff (or a plain description of changes) and produce a well-formed commit message following the [Conventional Commits](https://www.conventionalcommits.org/) specification. It chooses the right type (`feat`, `fix`, `chore`, `docs`, `refactor`, `test`, `style`, `perf`, `ci`), picks an appropriate scope, writes a concise subject line, and — when the change is large enough to warrant it — adds a descriptive body. Use this when you want consistent, meaningful commit history without having to remember the format every time. ## How to use ### Claude Code / Cline Copy this file to `.agents/skills/git-commit-writer/SKILL.md` in your project root. Then ask the agent: - *"Write a commit message for my staged changes using the Git Commit Writer skill."* - *"Here's a diff. Use the Git Commit Writer skill to produce a commit message."* For Claude Code, you can also run `git diff --staged` first and paste the output into the chat. ### Cursor Add the contents of the "Prompt / Instructions" section below to your `.cursorrules` file, or paste it into the Cursor AI pane before asking for a commit message. ### Codex Paste the diff into the Codex chat along with the instructions from the section below. Codex works best when you include the full diff rather than a summary. ## The Prompt / Instructions for the Agent When asked to write a commit message, follow these steps: 1. **Read the diff.** If ...