CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

commit-ko

AI(Claude 등)가 제안한 한글 커밋 메시지의 사무적·번역투 어휘("~을 수행함", "~을 진행함", "~적 개선을 실시함" 등)를 실제 개발자가 쓰는 자연스러운 한국어 커밋 메시지로 다듬는 스킬. humanize-korean과 달리 산문 문단이 아니라 1~2줄짜리 커밋 메시지 register에 특화되어 진단·청킹 없이 단일 콜로 즉시 처리한다. 트리거 — "커밋 메시지 자연스럽게", "커밋 메시지 다듬어줘", "이 커밋 메시지 AI 티 나", "commit message 한국어로 자연스럽게", "커밋 메시지 어색해", "커밋 메시지 사람처럼".

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A concise, well-structured instruction skill with a clear sequenced procedure, an explicit stop-condition, and proper offloading of the substitution table to a single one-level reference. The main weakness is a referenced maintenance/validation script (scripts/check_commit_lexicon_ids.py) that is not present in the bundle, creating a broken navigation link that also weakens the otherwise sound feedback-loop story.

Suggestions

Add the missing scripts/check_commit_lexicon_ids.py to the bundle (or remove the references to it in SKILL.md and commit-lexicon.md), so the advertised header/body ID-consistency validation is actually runnable.

Show one short before→after commit-message example inline in the 처리 절차 or 출력 section so the single-call action is immediately executable without opening the lexicon.

Add a one-line explicit feedback/recovery note for ambiguous cases (when a pattern match is uncertain), to push workflow_clarity toward the validation-loop anchor.

DimensionReasoningScore

Conciseness

Lean body of roughly 50 lines that assumes Claude's competence — it never explains what a commit message or Conventional Commits is, and uses tight bullets for input, principles, procedure, and output with every token earning its place.

5 / 5

Actionability

Concrete instruction-style guidance: step 2 enumerates specific target patterns (사무적 동사 수행/진행/실시, 한자어 명사화 -성/-적/-화, 과공손 종결, 영어 직역 구문 with by-passive/이중피동/have 직역 examples) and notes exceptions (굳은 외래어 제외); falls short of 5 because the actual substitution values live in the reference rather than inline, which is appropriate for progressive disclosure.

4 / 5

Workflow Clarity

A clear 4-step sequence with an explicit stop-condition checkpoint (step 3: if no patterns found, reply "이미 자연스러운 커밋 메시지입니다" and stop without forcing changes) plus explicit token-preservation rules; not a 5 because there is no error-recovery/feedback loop, though the single-call non-destructive nature makes that largely unnecessary.

4 / 5

Progressive Disclosure

Clean one-level-deep structure: SKILL.md is an overview that signals `references/commit-lexicon.md` (which exists) for the detailed substitution table; held below 5 because the body and lexicon both reference `scripts/check_commit_lexicon_ids.py` as a validation aid, but no scripts/ directory exists in the bundle, leaving a dead navigation link.

4 / 5

Total

17

/

20

Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, precise description written in third person that states a clear single-purpose action, distinguishes itself from a sibling skill, and supplies explicit natural-language trigger phrases. Its only limitation is that the described action is essentially singular (refine vocabulary), keeping specificity just below the comprehensive multi-action ceiling.

DimensionReasoningScore

Specificity

Names the concrete domain (Korean commit messages) and the specific action (다듬는/refines 사무적·번역투 어휘) with concrete target-pattern examples like "~을 수행함", "~을 진행함", "~적 개선을 실시함"; the core action is singular so it falls just short of the comprehensive multi-action anchor 5.

4 / 5

Completeness

Clearly answers both 'what' (refines AI-proposed Korean commit messages into natural developer-style ones, specialized for the 1-2 line commit register) and 'when' (explicit 트리거 block with concrete trigger phrases), matching the anchor that requires both with concrete triggers.

5 / 5

Trigger Term Quality

Provides a comprehensive set of natural trigger phrases users would actually say ("커밋 메시지 자연스럽게", "커밋 메시지 다듬어줘", "이 커밋 메시지 AI 티 나", "commit message 한국어로 자연스럽게", "커밋 메시지 어색해", "커밋 메시지 사람처럼") including synonyms and a Korean/English-mixed variant.

5 / 5

Distinctiveness Conflict Risk

Has a clear niche (commit-message register) and explicitly differentiates from the sibling prose skill ("humanize-korean과 달리 산문 문단이 아니라 1~2줄짜리 커밋 메시지 register에 특화"), giving it distinct triggers with minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

epoko77-ai/im-not-ai

Path

extras/skills/commit-ko/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.