git-commit-writer

Generate conventional commit messages from staged code diffs.

1|Updated Nov 16, 2025
One-click install
npx skills add https://github.com/bravegeek/ai-workshop --skill git-commit-writer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit-writer
Source: https://github.com/bravegeek/ai-workshop/tree/main/.gemini/skills/git-commit-writer
Command: npx skills add https://github.com/bravegeek/ai-workshop --skill git-commit-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you automatically craft clear, conventional commit messages based on your code changes, improving collaboration and history readability.

Core Features & Use Cases

  • Analyze diffs across modified files to determine the intent of changes.
  • Generate well-structured commit messages following conventional commit formats (feat:, fix:, docs:, refactor:, etc.).
  • Provide guidance for multi-part changes and optional body/footer details to capture context.

Quick Start

Stage your changes and run the git-commit-writer agent to receive a polished commit message you can apply.

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 conventional commit messages from git diffs?

To generate conventional commit messages from git diffs, you stage your changes and the skill analyzes the modified files to produce a structured message. It outputs a formatted subject and optional body based on the detected intent.

What is the conventional commit format for feature work and bug fixes?

The conventional commit format for feature work and bug fixes follows the type: scope: subject structure. This skill applies types like feat:, fix:, or refactor: to ensure your repository history remains standardized and readable.

Can I add a breaking change footer to an automated commit message?

Yes, you can add a breaking change footer to an automated commit message. The skill provides guidance for multi-part changes and can append detailed footers as needed to capture essential context for version control.

Does this workflow tool support analyzing diffs across any repository?

Yes, this workflow tool supports analyzing diffs across any repository. It guides you through code changes to determine the intent of modifications, applying to feature work, bug fixes, and refactors without platform restrictions.

What's the best way to write a commit message for multi-part code changes?

The best way to write a commit message for multi-part code changes is to analyze the diff and generate a structured subject with an optional body. This skill evaluates modified files to capture context and enforce conventional formats.