git-commit

Generate conventional commit messages from git diffs with type and scope detection.

66|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/jdiegosierra/contributor-report --skill git-commit-jdiegosierra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/jdiegosierra/contributor-report/tree/main/.agents/skills/git-commit
Command: npx skills add https://github.com/jdiegosierra/contributor-report --skill git-commit-jdiegosierra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create standardized, semantic git commits by analyzing diffs and generating conventional commit messages with intelligent staging, reducing human error and inconsistency.

Core Features & Use Cases

  • Auto-detect type and scope from changes and propose a conventional commit message
  • Generate messages that conform to the Conventional Commits specification
  • Interactive commit options to override type/scope/description and stage changes accordingly
  • Safe, incremental staging that groups related changes for clean history

Quick Start

Ask the AI to generate a conventional commit from the current diff and stage files accordingly.

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?

Automated conventional commit generation analyzes git diff output to suggest type, scope, and description. It auto-detects changes and proposes messages conforming to Conventional Commits specification, applicable to local workflows and CI pipelines.

What is the best way to stage related files for clean git history?

Safe incremental staging groups related changes from multi-file diffs to create clean history. It enables safe staged commits by analyzing changes and grouping related modifications together for semantic consistency.

Can I override the auto-detected type and scope in a generated commit message?

Interactive commit options allow you to override auto-detected type, scope, and description. You can manually adjust suggestions and stage changes accordingly before executing the final safe staged commit.

Does this conventional commit automation work in CI pipelines?

Conventional commit automation works in CI pipelines and local workflows. It handles single-file and multi-file changes by analyzing diff output, requiring access to git diff data to suggest appropriate commit messages.

What do I need to provide to analyze diffs and suggest conventional commits?

Diff analysis requires access to git diff output to generate conventional commit messages. No external dependencies are needed; the tool processes provided diffs to auto-detect type and scope for staging.