git-commit

Analyze git diffs to generate conventional commit messages and stage files.

37.6k|4.7k|Updated Jun 11, 2025
One-click install
npx skills add https://github.com/github/awesome-copilot --skill git-commit-github
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/github/awesome-copilot/tree/main/skills/git-commit
Command: npx skills add https://github.com/github/awesome-copilot --skill git-commit-github

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the creation of standardized, conventional commits by analyzing the actual diff and staging changes intelligently, reducing manual effort and error-prone messages.

Core Features & Use Cases

  • Auto-detects type and scope from changes to generate conventional commit messages.
  • Generates meaningful commit messages from diffs and supports overrides for type, scope, and description.
  • Performs intelligent file staging to group related changes before committing.

Quick Start

Describe the changes you want to commit, optionally specify type and scope, and run the skill to produce a conventional commit and apply it to the staged changes.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I automate creating conventional commit messages from my Git changes?

Conventional commits automate standardized messages by analyzing diffs to infer type and scope. This skill generates these messages automatically, reducing manual effort and ensuring consistency across your repository without requiring you to memorize formatting rules.

Can I override the auto-detected commit type and scope?

Yes, the skill supports optional overrides for type, scope, and description. After auto-detection analyzes your changes, you can manually specify these fields if the inferred values don't match your intent, giving you control while preserving automation benefits.

How does intelligent file staging work before committing?

Intelligent staging groups related changed files logically before committing, rather than staging everything at once. The skill analyzes which files belong together semantically, ensuring each commit captures a cohesive set of changes instead of mixing unrelated modifications.

What's the difference between this approach and writing commit messages manually?

Manual commits risk inconsistent formatting and incomplete descriptions. This skill analyzes actual diffs to generate precise, conventional messages automatically, eliminating typos, enforcing standards, and capturing meaningful context directly from code changes.

Can I use conventional commits across different repositories?

Yes, conventional commits are a standard format independent of repository structure. This skill applies the same auto-detection and staging logic across any Git repository, making it portable for teams managing multiple projects or monorepos.