git-commit

Create Git commits with conventional messages, emoji, and automated staging.

Updated Mar 10, 2026
One-click install
npx skills add https://github.com/Gamezar/opencode-cek --skill git-commit-gamezar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/Gamezar/opencode-cek/tree/main/plugins/git/skills/git-commit
Command: npx skills add https://github.com/Gamezar/opencode-cek --skill git-commit-gamezar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of well-formatted Git commits, ensuring consistency, clarity, and adherence to best practices, thereby improving code history and collaboration.

Core Features & Use Cases

  • Conventional Commits: Generates commit messages following the conventional commit format with appropriate emoji.
  • Automated Staging: Stages modified and new files if none are staged.
  • Branching Assistance: Prompts to create new branches from main or master for commits.
  • Pre-commit Checks: Automatically runs linters and build checks before committing (can be bypassed).
  • Commit Splitting: Analyzes diffs and suggests splitting large changes into multiple atomic commits.
  • Use Case: When you've made several related changes, this skill helps you craft a clear commit message, stage your files, and even suggests breaking down your work into smaller, more manageable commits if necessary.

Quick Start

Use the git-commit skill to create a new commit for your staged changes.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I automate creating conventional commit messages for my git changes?

Conventional commits follow a structured format like feat, fix, or chore, paired with a scope and description. This standard improves code review, generates automated changelogs, and makes version control history easier to read and collaborate on.

What is the best way to split large code diffs into smaller atomic commits?

Splitting large code diffs involves analyzing the changes and grouping related modifications into separate atomic commits. This logical separation improves code review clarity and ensures each commit represents a single, manageable update.

How do I run pre-commit hooks and linters before staging my files?

Running pre-commit hooks and linters before staging files requires automating the check during the commit process. This enforces code quality checks, and the execution can be bypassed if necessary for specific updates.

Does this automated commit process work with custom branch naming conventions for feature and fix branches?

Yes, automated commit processes support custom branch naming conventions for feature and fix branches. The system checks the current branch against your established patterns and prompts to create new branches from main or master if needed.

Why should I use AI to generate git commit messages instead of writing them manually?

Using AI to generate git commit messages ensures consistency and adherence to best practices that manual writing often misses. It analyzes the actual code diff to suggest accurate, structured conventional commit messages with appropriate emoji.