commit

Create and validate conventional commits with user confirmation.

15|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/sergio-bershadsky/ai --skill commit-sergio-bershadsky
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/sergio-bershadsky/ai/tree/main/plugins/git/skills/commit
Command: npx skills add https://github.com/sergio-bershadsky/ai --skill commit-sergio-bershadsky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically create conventional commits after task completion with explicit user confirmation, preventing messy history and accidental pushes.

Core Features & Use Cases

  • Generate conventional commits from staged changes using type, scope, and a concise description.
  • Preview diffs and require explicit user approval before finalizing a commit.
  • Enforce a safe workflow by never pushing changes to remote without explicit action.

Quick Start

Ask Claude to prepare a conventional commit for your latest changes and confirm when prompted.

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 with user approval before finalizing?

To generate conventional commits with user approval, the Skill automates type, scope, and description extraction from staged changes, previews the diff, and requires explicit human confirmation before finalizing the commit.

Can I preview a git diff and require explicit approval before committing changes?

Yes, you can preview a git diff and require explicit approval. The Skill integrates with git status to display staged changes and halts the commit process until you explicitly confirm the generated conventional commit message.

Does this conventional commit workflow automatically push changes to the remote repository?

No, this conventional commit workflow does not automatically push changes. It enforces a safe local development workflow by strictly preventing pushes to the remote repository without explicit action.

How do I extract the type and scope for a conventional commit from local feature branches?

To extract the type and scope for a conventional commit from local feature branches, the Skill analyzes your staged code changes and automatically drafts a strictly formatted message based on the conventional commits specification.

What is the best way to automate conventional commit formatting without accidental remote pushes?

The best way to automate conventional commit formatting safely is using a workflow that enforces strict formatting, generates draft messages from local diffs, and prevents pushing to remote without explicit action.

Are there limitations to automating git commits across different software projects?

A key limitation is that while it applies across local software projects and feature branches, it strictly prevents remote pushing, requiring separate manual actions to synchronize your local commits with the remote repository.