gh-commit

Create conventional git commit messages from repository changes.

484|76|Updated Oct 23, 2025
One-click install
npx skills add https://github.com/bastani-inc/atomic --skill gh-commit-bastani-inc
Or copy as Structured Prompt for Agentā–¼
Please help me install this Agent Skill.
Skill: gh-commit
Source: https://github.com/bastani-inc/atomic/tree/main/.agents/skills/gh-commit
Command: npx skills add https://github.com/bastani-inc/atomic --skill gh-commit-bastani-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you turn repository changes into clear, conventional commit messages without manually inspecting every file or worrying about commit format consistency.

Core Features & Use Cases

  • Commit Drafting: Reviews the current git status and diff to propose an appropriate commit message.
  • Change Grouping: Detects when multiple logical changes are present and suggests splitting them into separate commits.
  • Release-Friendly History: Uses conventional commit conventions so your history is easier to read, automate, and release from.
  • Use Case: Use it when you have a mixed set of edits, need a concise commit summary, and want the message to follow a standard format.

Quick Start

Use the gh-commit skill to inspect the current repository changes and create a conventional commit message for them.

Frequently Asked Questions about gh-commit

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 need a tool that inspects staged and unstaged repository changes and formats them into standard commit conventions. This Skill automates that by reviewing your repository status and diff to propose an appropriate commit message automatically.

When do I need to split logical changes into separate git commits?ā–¼

You need to split logical changes into separate git commits when your working directory contains mixed change sets that represent multiple features or fixes. This Skill detects multiple logical changes in your diff and suggests splitting them into distinct, release-friendly commits to preserve history clarity.

Does this Skill work with both staged and unstaged git edits?ā–¼

Yes, this Skill works with both staged and unstaged git edits. It requires diff inspection and repository status awareness to analyze all current edits, allowing it to draft conventional commit messages regardless of whether files are fully staged or still being modified.

What is the best way to format mixed change sets into conventional commits?ā–¼

The best way to format mixed change sets into conventional commits is to analyze the diff for distinct logical changes and group them accordingly. This Skill reviews mixed edits, proposes standard conventional commit formatting, and suggests splitting changes so your history remains easy to read and automate.

How does AI-authorship attribution work in generated commit messages?ā–¼

AI-authorship attribution in generated commit messages ensures the git history indicates that the commit message was created by an AI tool. This Skill preserves AI-authorship attribution while drafting conventional commit messages from your repository changes, maintaining transparency in your release-friendly history.