commit

Generate Korean Git commit messages from branch types and staged changes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of creating Git commits, ensuring they are well-formatted, descriptive, and adhere to project conventions, while also incorporating safety checks for sensitive files and build artifacts.

Core Features & Use Cases

  • Automated Commit Message Generation: Creates Korean commit messages based on branch type and code changes.
  • Pre-Commit Checks: Executes build commands and checks for sensitive files before committing.
  • Build Artifact Handling: Manages tracked build artifacts by suggesting .gitignore updates.
  • Contextual Synchronization: Suggests synchronizing domain contexts after a commit.

Quick Start

Use the commit skill to stage all changes and create a commit with an automatically generated message.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automatically generate Git commit messages from branch names and code diffs?

Automated Git commit message generation analyzes your branch naming conventions and staged code diffs to produce descriptive Korean commit titles and bodies, ensuring structured version control history without manual writing effort.

What pre-commit checks are needed to prevent sensitive files and build artifacts in Git?

Pre-commit safety checks detect sensitive files and execute build commands before committing. They also identify tracked build artifacts, suggesting `.gitignore` updates to prevent accidental exposure or repository bloat during version control operations.

Can I use branch naming conventions to format automated commit messages?

Yes, branch naming conventions are parsed to determine the commit type and context. This parsed branch information directly structures the generated commit title and body, aligning your automated commit messages with project standards.

What is the best way to handle tracked build artifacts during a Git commit?

The best way to handle tracked build artifacts is to detect them during pre-commit checks and suggest `.gitignore` updates. This prevents unwanted compiled files from entering version control while keeping your repository clean.

Does automated commit generation suggest post-commit actions for context synchronization?

Yes, after creating a commit, the automation suggests post-commit actions for context synchronization. This ensures your domain contexts and project state remain aligned with the newly committed code changes in version control.