commit

Generates Git commit messages following the Conventional Commits v1.0.0 format from staged changes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Hand-Tomi/text_bridge --skill commit-hand-tomi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/Hand-Tomi/text_bridge/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/Hand-Tomi/text_bridge --skill commit-hand-tomi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of creating Git commits that adhere to the project's Conventional Commits standard, ensuring consistency and clarity in version control history.

Core Features & Use Cases

  • Conventional Commits: Generates commit messages following the type(scope): description format.
  • Automated Git Commands: Executes necessary Git commands for status checking, diffing, and committing.
  • Use Case: After making several code changes, you can ask the AI to commit them with a message like "feat(auth): implement two-factor authentication", and it will handle the Git operations and message formatting.

Quick Start

Ask the AI to commit your staged changes with a message describing the new feature.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate conventional commits automatically from staged changes?

To generate conventional commits, the Skill analyzes your staged changes using git diff and git status, then formats the output into the type(scope): description structure defined by Conventional Commits v1.0.0. It supports types like feat, fix, and docs.

What is the conventional commit format for a breaking change in git?

The conventional commit format for a breaking change uses a specific commit type like feat or fix, an optional scope, and a breaking change indicator to denote incompatible API modifications, strictly following the v1.0.0 standard for version control clarity.

How do I commit code with a specific type and scope using conventional commits?

To commit code with a specific type and scope, you ask the AI to commit staged changes with a desired message like feat(auth): implement login. The Skill executes the git commit operation while adhering to the requested conventional format.

Does this conventional commit tool execute destructive git commands or force pushes?

No, this conventional commit tool strictly avoids destructive git commands and unauthorized pushes. It only executes necessary Git operations for status checking, diffing, and committing staged changes to ensure safe version control management.

What git commit types are supported for code management automation?

Supported git commit types for code management automation include feat, fix, docs, style, refactor, test, chore, perf, ci, and build. Each type can include an optional scope and breaking change indicator for precise version control.