git-commit

Generate conventional git commits from diffs with type and scope detection.

1|Updated Jan 30, 2023
One-click install
npx skills add https://github.com/ncksol/ravebot --skill git-commit-ncksol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/ncksol/ravebot/tree/main/.github/skills/git-commit
Command: npx skills add https://github.com/ncksol/ravebot --skill git-commit-ncksol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually crafting git commit messages is error-prone and inconsistently formatted. This Skill automatically analyzes code changes to generate conventional, semantic commits that follow the Conventional Commits spec, reducing drift and confusion in history.

Core Features & Use Cases

  • Auto-detects type and scope from changes to produce accurate commit messages
  • Generates conventional commit messages from diffs with optional body and footer support
  • Interactive commit workflow allowing type, scope, and description overrides
  • Intelligent staging for logical grouping of related changes
  • Safe, best-practice guidance and guardrails to prevent accidental secrets disclosure

Quick Start

Run the commit tool to stage your changes and generate a compliant commit description.

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 automatically, you can use a tool that analyzes code changes to detect the type and scope, producing semantic commit descriptions without manual formatting.

Can I override the type and scope of an auto-generated git commit?

Yes, you can override the auto-generated type and scope of a git commit through an interactive workflow, allowing you to manually adjust the commit description, scope, and type before executing the staged commit.

How does intelligent staging work for grouping related git changes into commits?

Intelligent staging for grouping related git changes works by analyzing multi-file diffs to logically group related modifications together, ensuring that each generated commit represents a cohesive and semantic set of changes.

What is the best way to prevent accidental secret leaks in git commit messages?

The best way to prevent accidental secret leaks in git commits is to use automated safety checks and guardrails that scan diffs during the commit generation process to ensure correct formatting and block sensitive data disclosure.

Does this automated commit tool support multi-file changes across feature branches and bug fixes?

Yes, this automated commit tool supports multi-file changes across feature branches and bug fixes, applying diff analysis to generate compliant conventional commits for complex software development workflows.