git-commit

Guide Git staging, splitting, and Conventional Commits with emoji.

4|1|Updated Mar 24, 2024
Ready to run
npx skills add https://github.com/ruan-cat/monorepo --skill git-commit-ruan-cat
💬 Prompt for ChatGPT / Claude Chat▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/ruan-cat/monorepo/tree/main/claude-code-marketplace/common-tools/skills/git-commit
Command: npx skills add https://github.com/ruan-cat/monorepo --skill git-commit-ruan-cat

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill guides you to review and stage only the changes you intend to commit, split work into logical commits, and write clear, conventional messages that include emoji when desired.

Core Features & Use Cases

  • Enforces Conventional Commits: Ensures commit messages follow a consistent format with optional emoji.
  • Guided Staging & Splitting: Helps you select changes to include in each commit and split large changes into meaningful chunks.
  • Contextual Recommendations: Suggests scope, type, and message body based on code changes.
  • Use Case: When preparing a feature, bug fix, or refactor, this tool helps craft clean, reviewable commits across multiple commits.

Quick Start

Describe the changes you want to commit, and the tool will help you stage, split, and craft conventional commit messages with emoji.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I write conventional commits with emoji for my git workflow?▼

To write conventional commits with emoji, you describe your intended changes to guide the staging and splitting process. This produces clear, searchable git history by enforcing conventional commit formats with optional emoji and contextual scope definitions.

What is the best way to split large code changes into logical git commits?▼

The best way to split large changes into logical commits is through guided staging. You review and stage only the intended modifications, then split the work into meaningful chunks to ensure each commit represents a precise, reviewable unit of code.

How do I stage only specific code changes for a precise git commit?▼

To stage specific changes for a precise git commit, you use guided staging to select intended modifications. This workflow applies to software projects of various sizes, ensuring you stage only relevant changes before generating a meaningful commit message.

Does this conventional commit tool support contextual scope definitions for code review?▼

Yes, this conventional commit tool supports contextual scope definitions for code review. It suggests scope, type, and message body based on your actual code changes, helping you craft clean, reviewable commits across multiple logical chunks.

Why should I use conventional commits instead of plain text git commit messages?▼

You should use conventional commits instead of plain text to produce a clean, searchable project history. Enforcing a consistent format with optional emoji makes commits easier to review and understand across software projects of various sizes.