commit
Automates the process of analyzing diffs and creating standardized, conventional commit messages.
Install
mkdir -p .claude/skills/commit-chnu-kim && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17416" && unzip -o skill.zip -d .claude/skills/commit-chnu-kim && rm skill.zipInstalls to .claude/skills/commit-chnu-kim
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
변경 분석 → 커밋 메시지 생성 → 커밋Key capabilities
- →Analyze changes using `git status` and `git diff`
- →Reference existing commit styles from `git log`
- →Determine commit type (feat/fix/refactor/style/test/docs/chore)
- →Generate commit messages in Conventional Commits format
- →Validate build with `pnpm build`
- →Stage and commit changes, excluding sensitive files
How it works
The skill analyzes changes, determines the commit type, generates a Conventional Commits message, validates the build, and then stages and commits the changes.
Inputs & outputs
When to use commit
- →Generate commit message for new feature
- →Automate commit documentation
- →Maintain consistent commit history
About this skill
현재 변경을 커밋한다. 인자가 있으면 커밋 범위나 메시지에 대한 힌트로 사용한다: $ARGUMENTS
git status,git diff,git diff --cached,git log --oneline -10으로 변경과 최근 메시지 스타일을 파악한다.- 변경이 서로 무관한 여러 작업을 섞고 있으면 논리 단위로 나눠 여러 커밋을 제안한다. 이번 작업과 무관해 보이는 파일(사용자의 진행 중 작업, 임시 스크립트 등)은 임의로 포함하지 말고 물어본다.
- 메시지:
type: 한국어 요약한 줄(50자 안팎). 타입은feat/fix/refactor/style/test/docs/chore. 이유가 diff만으로 드러나지 않으면 본문에 "왜"를 적는다. - 코드 변경이 포함되면
pnpm test와pnpm build를 통과시킨 뒤 커밋한다. 실패하면 커밋하지 않고 원인을 보고한다. 문서·하네스만 바뀐 경우는 생략한다. - 파일을 경로로 지정해 스테이징한다 (
git add -A금지)..env*, 자격 증명,.dev.vars는 절대 스테이징하지 않는다. - main/master 브랜치라면 커밋 전에 브랜치를 만들지 사용자에게 확인한다.
끝나면 커밋 해시와 메시지를 짧게 보고한다.
When not to use it
- →Committing without build validation
- →Committing sensitive files
Limitations
- →Requires `git-committer` agent
- →Requires `pnpm build` for build validation
- →Excludes sensitive files from staging and committing
How it compares
This skill automates the process of analyzing changes, generating Conventional Commits messages, and validating the build before committing, ensuring consistent and validated commit history unlike manual commit creation.
Compared to similar skills
commit side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| commit (this skill) | 0 | 7mo | No flags | Beginner |
| resolve-conflicts | 81 | 11mo | Review | Intermediate |
| openspec-onboard | 10 | 8mo | Review | Beginner |
| codex-cli-bridge | 9 | 12mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
resolve-conflicts
antinomyhq
Use this skill immediately when the user mentions merge conflicts that need to be resolved. Do not attempt to resolve conflicts directly - invoke this skill first. This skill specializes in providing a structured framework for merging imports, tests, lock files (regeneration), configuration files, and handling deleted-but-modified files with backup and analysis.
openspec-onboard
studyzy
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
codex-cli-bridge
alirezarezvani
Bridge between Claude Code and OpenAI Codex CLI - generates AGENTS.md from CLAUDE.md, provides Codex CLI execution helpers, and enables seamless interoperability between both tools
skill-sync
KyleKing
Syncs Claude Skills with other AI coding tools like Cursor, Copilot, and Codeium by creating cross-references and shared knowledge bases. Invoke when user wants to leverage skills across multiple tools or create unified AI context.
github-workflow-automation
ruvnet
Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management
git-advanced-workflows
wshobson
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.