git-commit

Create conventional commits from staged or unstaged changes with diff-based messages.

4|Updated Oct 6, 2025
One-click install
npx skills add https://github.com/otrebu/agents --skill git-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/otrebu/agents/tree/main/skills/git-commit
Command: npx skills add https://github.com/otrebu/agents --skill git-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the tedious and often inconsistent manual process of creating Git commits. It ensures your commit history is clean, readable, and adheres to conventional commit standards, reducing mental overhead and improving collaboration.

Core Features & Use Cases

  • Conventional Commits: Automatically stages changes and generates commit messages following established conventions (e.g., feat, fix, refactor).
  • Diff Analysis: Intelligently analyzes your code changes to suggest the most appropriate commit type and scope.
  • Optional Push: Seamlessly integrates with post-commit push operations, allowing you to commit and push in one go.
  • Use Case: After making a series of code changes, simply tell Claude "commit my changes and push." It will stage your files, craft a perfectly formatted conventional commit message based on your diff, and push it to the remote, ensuring a pristine Git history without manual effort.

Quick Start

Use the git-commit skill to commit all staged changes with a conventional commit message and push to the remote.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I create conventional commits automatically from my code changes?

Conventional commits are standardized Git messages following a format like `feat:` or `fix:` that organize your history. This Skill analyzes your diffs, stages changes, and generates commit messages with the correct type, scope, and description automatically, eliminating manual formatting.

Can I commit and push to my remote repository in one step?

Yes. This Skill stages your changes, creates a conventional commit message based on your diff analysis, and optionally pushes to the remote in a single workflow, reducing friction between local commits and publishing.

How does the Skill determine the commit type and scope from my changes?

The Skill intelligently analyzes your code diffs to infer whether changes are features, fixes, refactors, or other types, then derives the scope from the modified files or functions. This produces accurate conventional commit messages without manual categorization.

Does it handle selective staging of files or exclude sensitive data?

Yes. The Skill supports selective staging of specific files, ensures atomic commits by grouping related changes, and excludes sensitive files from staging to maintain security while creating multiple commits in one workflow.

What if I have multiple sets of changes that should become separate commits?

The Skill supports multiple commits in a single workflow, intelligently grouping related changes and generating distinct conventional commit messages for each atomic unit, keeping your Git history organized.

Why should I use conventional commits instead of writing my own messages?

Conventional commits standardize your history across teams, improve readability for tools like changelog generators, and reduce cognitive load. This Skill enforces the format automatically, ensuring consistency without manual discipline.