git-master

Git expert for atomic commits, rebasing, and history management

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/git-master/SKILL.md

Quality

Content

92%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.

The body is a tight, well-organized routing skill that assumes Claude's competence and makes the single action unambiguous. The only minor gap is the lack of a concrete example task or handling note for non-git input.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient ("Routes to the git-master agent for git operations") with no over-explanation of concepts Claude already knows; every token earns its place.	5 / 5
Actionability	It gives concrete, executable routing ("/git-master <git task>" and "Use /prompts:git-master with the user task."), but provides no example task and does not show how to handle non-git inputs, leaving a minor gap.	4 / 5
Workflow Clarity	As a single-purpose routing skill, the single action (route to /prompts:git-master) is unambiguous, which satisfies the simple-skill exception for a 5.	5 / 5
Progressive Disclosure	The skill is under 50 lines, needs no external references, and is organized into clear sections (Usage, Routing, Capabilities), meeting the simple-skill exception for a 5.	5 / 5
	Total	19 / 20 Passed

Description

53%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.

The description clearly establishes a git-focused niche with several concrete task areas, but lacks an explicit "Use when..." trigger clause and richer natural-language keywords. It is solid but stops short of the most complete, trigger-rich examples.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user needs to write atomic commits, rebase branches, or clean up git history.'

Broaden trigger terms with natural synonyms users say, such as 'commit', 'squash', 'merge', 'rewrite history', or 'split commits'.

Spell out 1-2 more concrete actions (e.g. 'split commits, squash history, resolve rebase conflicts') to lift specificity toward level 4-5.

Dimension	Reasoning	Score
Specificity	The description names the git domain and 2-3 concrete task areas ("atomic commits, rebasing, and history management"), but these are task categories rather than the granular, listed actions of the level-4 anchor.	3 / 5
Completeness	It gives a clear "what" (git expert for atomic commits, rebasing, history management) but has no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	"atomic commits", "rebasing", and "history management" are relevant git terms, but common natural variations (e.g., "commit", "squash", "merge", "git history") are missing.	3 / 5
Distinctiveness Conflict Risk	The git-specific niche (atomic commits, rebasing, history management) is mostly distinct with only minor overlap risk against a generic git skill, fitting the level-4 anchor.	4 / 5
	Total	13 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Yeachan-Heo/oh-my-codex
Path: skills/git-master/SKILL.md
Commit: e94437f

Reviewed: 8 days ago

Table of Contents

Discovery Implementation Validation

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.