git-commit

Generates conventional commit messages and stages files from diffs.

1|1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/PedroHBO/opencode-config-skills --skill git-commit-pedrohbo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/PedroHBO/opencode-config-skills/tree/main/skills/git-commit
Command: npx skills add https://github.com/PedroHBO/opencode-config-skills --skill git-commit-pedrohbo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of conventional commit messages and intelligently stages files based on diffs, reducing cognitive load during code reviews.

Core Features & Use Cases

  • Auto-detects commit type and scope from changes
  • Generates conventional commit messages from diffs
  • Interactive commit with optional type/scope/description overrides
  • Intelligent file staging for logical grouping
  • Supports breaking-change markers and bodies

Quick Start

Ask me to commit the current changes and I will generate a conventional commit message and handle staging automatically.

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 automatically from git diffs?

You can generate conventional commit messages by asking the Skill to commit current changes; it auto-detects type and scope from diffs, creates semantic messages, and handles staging decisions interactively.

What is intelligent file staging for logical grouping in git?

Intelligent file staging for logical grouping is a process that reviews your code diffs and interacts with you to stage related files together. This ensures each commit represents a coherent logical unit rather than mixing unrelated changes.

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

Yes, you can override the auto-detected commit type and scope. The Skill provides interactive prompts allowing you to manually adjust the type, scope, and description before finalizing the commit.

Does this git commit automation support breaking-change markers and commit bodies?

Yes, this git commit automation supports breaking-change markers and commit bodies. It detects and formats breaking changes according to conventional commit standards, appending detailed bodies to explain the diff context.

What is the best way to maintain a structured git history for semantic versioning?

The best way to maintain a structured git history for semantic versioning is automating conventional commit message generation from diffs. This ensures consistent semantic formatting across projects and logical file grouping for cleaner code reviews.