git-commit

Generate conventional git commits by analyzing diffs and staging changes.

Updated Feb 7, 2026
One-click install
npx skills add https://github.com/adacosdev/plan-eat --skill git-commit-adacosdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/adacosdev/plan-eat/tree/main/.agents/skills/git-commit
Command: npx skills add https://github.com/adacosdev/plan-eat --skill git-commit-adacosdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers create standardized, semantic git commits by analyzing diffs, determining type and scope, and staging changes intelligently.

Core Features & Use Cases

  • Auto-detects type and scope from changes and suggests conventional commit messages.
  • Generates conventional commit messages from diffs and applies them to commits.
  • Interactive commit with optional type, scope, and description overrides.
  • Intelligent staging to group related changes for a single commit.

Quick Start

Describe the changes you've made and ask the AI to generate and apply a conventional commit.

Frequently Asked Questions about git-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 automatically?

To generate conventional commit messages from git diffs, this skill analyzes your changes and auto-detects the type and scope. It then suggests a standardized message and stages the related changes for a single commit.

Can I override the type and scope during an interactive git commit?

Yes, you can override the type, scope, and description during an interactive git commit. The skill suggests conventional commit messages but allows you to interactively adjust these fields before finalizing the commit.

What is the best way to group related file changes into a single staged commit?

The best way to group related file changes into a single staged commit is using intelligent staging. This skill analyzes your diffs and automatically stages related changes together to ensure a logical, cohesive commit history.

Does this skill work across typical software projects for version control automation?

Yes, this version control automation works across typical software projects. It analyzes diffs and generates conventional commits regardless of your specific software engineering workflow.

Why should I use conventional commits for my git commit history?

You should use conventional commits to create a standardized, semantic git commit history. By analyzing diffs to determine type and scope, this approach ensures consistent commit messages across typical software projects.