git-commit

Generate conventional git commit messages from repository changes.

8|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/OiAnthony/.agents --skill git-commit-oianthony
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/OiAnthony/.agents/tree/main/skills/git-commit
Command: npx skills add https://github.com/OiAnthony/.agents --skill git-commit-oianthony

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of writing and formatting git commits by turning a change set into a clear, conventional commit message and helping you stage the right files for a single logical commit.

Core Features & Use Cases

  • Diff Analysis: Reviews staged or unstaged changes to infer the right commit type, scope, and concise description.
  • Intelligent Staging: Helps group related files before committing so each commit stays focused and easy to review.
  • Safe Git Workflow: Follows commit hygiene rules, avoids secrets, and respects hook and history safety boundaries.
  • Use Case: Use it when you have a mixed set of code, docs, and config edits and want one polished commit message that matches the actual change.

Quick Start

Ask the Skill to inspect your git changes and create a conventional commit message, staging any needed files only after confirming the logical change group.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I generate a conventional commit message from git diff?

To group related files for staging before committing, the Skill analyzes your repository changes to help you stage the right files. This ensures each commit stays focused on a single logical change group and is easy to review.

Can I commit unstaged changes or do I need to stage files first?

You can commit unstaged changes as the Skill applies diff analysis to both unstaged and staged code, documentation, and configuration edits. It selects files for staging and infers the commit type and scope only after confirming the logical change group.

Does this git commit workflow bypass hooks or run destructive commands?

This git commit workflow does not bypass hooks or run destructive commands. It follows Git safety rules that avoid secrets, destructive commands, and hook bypassing to ensure history safety boundaries are respected.

What is the best way to write conventional commits for mixed code and config changes?

The best way to write conventional commits for mixed code and config changes is to use diff inspection to infer the correct type and scope. The Skill turns mixed change sets into one polished conventional commit message matching the actual change.