git-commit

Analyzes diffs and generates conventional git commits with optional interactive overrides.

Updated Feb 27, 2026
One-click install
npx skills add https://github.com/pau-vega/react-router-drizzle --skill git-commit-pau-vega
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/pau-vega/react-router-drizzle/tree/main/.agents/skills/git-commit
Command: npx skills add https://github.com/pau-vega/react-router-drizzle --skill git-commit-pau-vega

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of conventional git commits by analyzing diffs and generating semantic messages to ensure consistency and better changelogs.

Core Features & Use Cases

  • Analyze diffs to determine an appropriate type, scope, and description following the Conventional Commits spec.
  • Intelligent staging and grouping of changes for logical commits, with guidance to keep one logical change per commit.
  • Interactive commit with optional overrides for type, scope, and description to suit edge cases.
  • Enforce best practices and safety checks, including avoiding secrets exposure and referencing related issues.

Quick Start

Analyze the current changes to generate and perform 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 commits automatically from git diffs?

To generate conventional commits from git diffs, this Skill analyzes your staged or unstaged changes to determine the appropriate type, scope, and description, then executes the commit with semantic messages following the conventional commits spec.

Can I override the generated commit type and scope interactively?

Yes, you can override the generated commit type, scope, and description interactively to handle edge cases, ensuring the final commit message accurately reflects your specific changes while still enforcing best practices.

Does this tool support staging changes before creating a conventional commit?

Yes, it supports conditional staging by intelligently grouping changes for logical commits, guiding you to keep one logical change per commit while analyzing diffs for both staged and unstaged modifications.

What safety checks are enforced when automating git commit messages?

Safety guardrails enforce best practices by checking for secrets exposure and referencing related issues, ensuring your automated conventional commits remain secure and properly documented.

When do I need to use conventional commits for my repository changes?

You need conventional commits when you want to ensure consistency across features, fixes, docs, and maintenance changes, which ultimately results in better changelogs and more semantic versioning.