Git Commit Writer

Generate conventional commit messages from git diffs or change descriptions.

9|1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Notysoty/openagentskills --skill git-commit-writer-notysoty
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Git Commit Writer
Source: https://github.com/Notysoty/openagentskills/tree/main/skills/git-commit-writer
Command: npx skills add https://github.com/Notysoty/openagentskills --skill git-commit-writer-notysoty

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reads a git diff (or a plain description of changes) and produces a well-formed commit message that adheres to the Conventional Commits specification. It automatically selects the appropriate type (feat, fix, chore, docs, refactor, test, style, perf, ci), suggests a suitable scope, crafts a concise subject line, and appends a descriptive body when the change warrants it.

Core Features & Use Cases

  • Read a git diff or change description and output a conventional commit message.
  • Automatically determine type, scope, and subject; optionally include a body for larger changes.
  • Support multiple environments or agent surfaces: Claude Code, Cursor, Codex, and other integrations.
  • Use case: preserve consistent, readable commit history across a codebase.

Quick Start

Ask the agent to generate a conventional commit message from the current git diff.

Frequently Asked Questions about Git Commit Writer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a conventional commit message from a git diff?

To generate a conventional commit message from a git diff, the Skill analyzes your staged changes or plain change descriptions to determine the appropriate type, scope, and subject line. It outputs a properly formatted commit message suitable for version control.

Can I automatically determine the correct commit type and scope for my changes?

Yes, you can automatically determine the correct commit type and scope for your changes. The Skill reads your git diff and selects the appropriate type like feat, fix, or chore, suggests a suitable scope, and formats a concise subject line.

Does this conventional commit generator work with Claude Code and Cursor?

This conventional commit generator supports multiple environments and agent surfaces including Claude Code, Cursor, and Codex. It processes plain change descriptions or staged diffs across these integrations to output well-formed commit messages.

What is the best way to format breaking changes and issue references in commit messages?

The best way to format breaking changes and issue references is to append them as an optional footer. The Skill generates a commit message that includes an optional breaking-change footer or issue references based on the provided git diff.

When do I need to add a body to my conventional commit message?

You need to add a body to your conventional commit message when the change warrants additional descriptive context. The Skill appends a descriptive body for larger changes while maintaining a concise subject line for smaller diffs.