commit

Generate semantic Git commit messages from staged code changes.

Updated Feb 13, 2026

Search Tags:#git #code review #version control #development workflow #commit #semantic commits

Ready to run

npx skills add https://github.com/aubrian-halili/ai-experience --skill commit-aubrian-halili

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/aubrian-halili/ai-experience/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/aubrian-halili/ai-experience --skill commit-aubrian-halili

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of creating well-formatted, semantic Git commit messages, ensuring consistency and clarity in your project's history.

Core Features & Use Cases

Semantic Commit Generation: Automatically generates commit messages following conventional commit standards.
Safety-First Approach: Guides users to stage specific files, warns about sensitive data, and requires explicit confirmation before committing.
Use Case: When you've completed a new feature, use this Skill to help you write a commit message like FEAT(auth): Implement two-factor authentication after reviewing your staged changes.

Quick Start

Use the commit skill to create a new commit with the message "Implement user profile editing".

Frequently Asked Questions about commit

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

FAQPage Schema

How do I generate semantic Git commit messages based on staged changes?▼

Generate semantic Git commit messages by analyzing staged code changes against project conventions. This process formats commits automatically, supporting atomic commits, amending previous commits, and handling breaking changes.

What is the best way to enforce safety rules when staging specific files in Git?▼

Enforce Git safety rules by staging specific files individually and scanning for sensitive data before committing. This approach requires explicit confirmation before finalizing the commit to prevent accidental exposure.

How do I write conventional commit messages for breaking changes in version control?▼

Write conventional commit messages for breaking changes by applying semantic standards to your development workflow. The generation process identifies breaking changes and formats the commit message to reflect the update.

Can I use an automated development workflow to amend previous Git commits?▼

Yes, you can amend previous Git commits within an automated development workflow. The process supports amending existing commits while maintaining semantic formatting and enforcing safety rules for staged files.

Does the semantic commit generation process require explicit confirmation before committing?▼

Yes, semantic commit generation requires explicit confirmation before committing to ensure safety. The process reviews staged code changes and warns about sensitive data before finalizing the version control update.