commit

Analyze git state and generate conventional commits with Korean subjects.

15|6|Updated Oct 18, 2014
One-click install
npx skills add https://github.com/ujuc/dotrc --skill commit-ujuc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/ujuc/dotrc/tree/main/claude/skills/commit
Command: npx skills add https://github.com/ujuc/dotrc --skill commit-ujuc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of git commits following your team's version control guidelines, saving time and ensuring consistent, review-friendly messages.

Core Features & Use Cases

  • State-aware Committing: Analyze staged/unstaged changes and propose or create conventional commits.
  • Structured Messages: Enforce the subject/body/footer format with rationale and attributions.
  • Use Case: When you need to commit several changes, this Skill builds a well-formed commit message that explains the why and what, reducing review churn.

Quick Start

To begin, invoke the commit workflow on the current repository; the Skill will analyze the git state, determine the appropriate commit type, and generate a well-formed commit message following your guidelines.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate git commit messages that follow conventional commit guidelines?

Conventional commits automate git commit messages by analyzing your staged changes, determining the commit type (feat, fix, etc.), and generating a structured message with subject, body, and footer. This Skill generates Korean-language commits with -하다 endings and enforces 72-character body wrapping to maintain consistency across your team's workflow.

Can I use automated commits with my existing git workflow?

Yes. This Skill analyzes your repository's current staged and unstaged state, then proposes or creates well-formed commits without disrupting your existing git workflow. It applies conventional commit standards while respecting your version-control guidelines and team conventions.

What's the best way to ensure consistent commit messages across a team?

Enforcing a commit message structure reduces review churn and improves clarity. This Skill generates commits following conventional commit format with rationale and attribution footers, ensuring every message explains the why and what in a standardized, reviewable format that your team can rely on.

How do conventional commits improve code review?

Conventional commits structure messages with a clear subject explaining the change type and scope, a detailed body explaining rationale, and footers for attribution. This format helps reviewers understand intent immediately, reduces back-and-forth questions, and creates a searchable commit history that documents decision reasoning.

Does this Skill support non-English commit messages?

Yes. This Skill specializes in generating Korean-language commits with appropriate grammatical structure, including -하다 verb endings and proper formatting conventions for Korean technical writing in commit subjects and bodies.