commit

Automates Korean commit messages from parsed Git branch names and performs predefined checks before committing.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/rnqhstmd/oh-my-bakedpotato --skill commit-rnqhstmd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/rnqhstmd/oh-my-bakedpotato/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/rnqhstmd/oh-my-bakedpotato --skill commit-rnqhstmd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill standardizes commit messages by deriving a Korean message from the branch name and performing pre-checks to ensure quality before commit.

Core Features & Use Cases

  • Branch-type parsing to generate consistent, localized commit messages.
  • Pre-checks including test execution and sensitive file detection before committing.
  • Use case: teams using a branch-based workflow ensure every commit is a clear, Korean message that reflects the change set.

Quick Start

Create a branch-aware Korean commit message from the current branch while performing pre-checks for tests and sensitive files.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate Korean git commit messages from branch names?

Pre-checks for git commits involve running tests and detecting sensitive files before finalizing the commit. This skill integrates these pre-check steps automatically to enforce quality guardrails and prevent sensitive data from being committed.

What is branch-aware commit message generation in version control?

Branch-aware commit message generation is a process that derives standardized messages by parsing the branch type. It automates consistent, localized Korean commit messages by analyzing the branch name and extracting change summaries via diff.

How do I run pre-checks for tests and sensitive files before a git commit?

You can run pre-checks for tests and sensitive files before a git commit by integrating automated scanning steps. This skill enforces these guardrails by executing tests and scanning files for sensitive data prior to committing changes.

Can I generate standardized Korean commit messages for team-based git workflows?

Yes, you can generate standardized Korean commit messages for team-based git workflows. This skill uses branch-type parsing and diff extraction to ensure every team member creates clear, localized messages that reflect their specific change set.

What are the limitations of automating commit messages from branch names?

Automating commit messages from branch names relies on strict branch naming conventions to parse types correctly. If branch names are unstructured, the generated Korean commit messages may lack accuracy, and pre-checks require tests and file scans to be properly configured.