commit

Generate conventional Git commit messages from staged changes and session history.

Updated Aug 27, 2026

Search Tags:#automation #git #development #version control #commit #code

Ready to run

npx skills add https://github.com/grafana/sigil --skill commit-grafana

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/grafana/sigil/tree/main/.agents/skills/commit
Command: npx skills add https://github.com/grafana/sigil --skill commit-grafana

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of well-formed Git commit messages, ensuring your commit history is clear, informative, and consistent.

Core Features & Use Cases

Automated Commit Message Generation: Creates commit messages based on session history and code changes.
Convention Adherence: Follows common Git conventions (type prefix, subject, wrapped body).
Rationale Inclusion: Incorporates the 'why' behind changes into the commit body.
Use Case: After making several code changes, you can ask this Skill to prepare a commit message that summarizes your work and explains the reasoning, ensuring a professional and understandable history.

Quick Start

Use the commit skill to create a git commit from your current staged changes.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I automatically generate a git commit message from staged changes?▼

You can automatically generate a git commit message by inspecting your staged changes and session history. The commit skill analyzes your git status and diffs to create a message with a type prefix, short subject, and a wrapped body explaining the summary and rationale behind the code changes.

What is the best way to write conventional git commit messages with a rationale?▼

The best way to write conventional git commit messages is to follow standard git conventions including a type prefix, short subject, and wrapped body. This automated approach uses session history to include the rationale and summary, ensuring a clear and informative version control history.

Does automated commit message generation work with unstaged new files?▼

Yes, automated commit message generation works with unstaged new files by inspecting git status and diffs before writing. The process stages new files as needed to ensure the generated commit message accurately reflects all current code changes in your development environment.

How do I format a git commit body to include the reasoning behind code changes?▼

To format a git commit body with reasoning, the commit generation process incorporates the 'why' behind changes from your session history. This creates a wrapped body containing a summary and rationale, ensuring your version control history remains professional and understandable.

Can I use automated commit writing for development automation without manual typing?▼

You can use automated commit writing for development automation to eliminate manual typing. By analyzing current diffs and session context, it automatically stages files and crafts a well-formed message following common git conventions, streamlining your version control workflow.