git-master

Handles git work: atomic commits, rebase, squash, blame, bisect, reflog, and history questions. Use whenever a task needs a commit or a git-history investigation; skip for ordinary code edits.

Quality

95%

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

Quality

Content

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

An exceptionally well-built operational skill: exact commands, safety gates, and validation checkpoints for destructive git operations with zero padding. The sole structural weakness is the PR-attachment section, which references an out-of-bundle document and sits outside the skill's core scope.

Suggestions

Move the PR Body Evidence Attachments section into a separate reference file in a references/ bundle directory (or drop it if the referenced docs/reference/github-attachment-upload.md is repo-specific), keeping SKILL.md focused on commit, rebase, history, and status modes.

If the attachment guidance stays inline, link it as a proper relative bundle path (e.g. references/github-attachment-upload.md) so the referenced file ships with the skill and the reference is verifiable.

Dimension	Reasoning	Score
Conciseness	Lean and efficient throughout — no concept explanations of git basics, every section carries operational weight (mode gate, safety checks, command selection rules), and the ground-truth command block is presented without narration. Matches 'every token earns its place', not the 'minor instances of over-explanation' anchor below.	5 / 5
Actionability	Fully executable guidance: copy-paste-ready commands with exact flags ("GIT_SEQUENCE_EDITOR=: git rebase -i --autosquash <base>", "--force-with-lease", "git log -S", "git blame -L start,end -- file") covering the common commit, rebase, and history cases. This is the top anchor, a step above 'concrete commands with minor gaps'.	5 / 5
Workflow Clarity	Clear mode classification, a pre-write safety checklist, per-commit verification ("verify git diff --staged --stat" before, "git log -1 --oneline" after), post-rebase smoke checks, and explicit recovery paths (rebase --abort, reflog). Destructive operations have feedback loops, so the destructive-cap is not triggered and the full validation anchor fits.	5 / 5
Progressive Disclosure	Well-organized single-file structure with clear section navigation, but the "PR Body Evidence Attachments" section references "docs/reference/github-attachment-upload.md" — a repo-relative path outside the skill bundle that cannot be verified as a real skill reference — and is tangential to the skill's stated git scope. Fits 'good structure with minor organization gaps' rather than the clean one-level-deep reference structure of the top anchor.	4 / 5
	Total	19 / 20 Passed

Description

92%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 description: concrete capability list, explicit trigger and skip guidance, and a clearly bounded niche. The only improvement space is broader synonym coverage for git tasks users phrase differently (revert, cherry-pick, undo).

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — "atomic commits, rebase, squash, blame, bisect, reflog, and history questions" — giving comprehensive coverage of the git-history domain with no meaningful gaps, matching the top anchor rather than the 'minor gaps' anchor below it.	5 / 5
Completeness	Explicitly answers both 'what' (the enumerated git operations) and 'when' ("Use whenever a task needs a commit or a git-history investigation"), plus a negative trigger ("skip for ordinary code edits") — clearly the top anchor, not the 'when could be more explicit' anchor below.	5 / 5
Trigger Term Quality	Good keyword coverage with natural phrases users would say ("commit", "rebase", "squash", "blame", "git-history investigation"), but common variations like "revert", "undo a commit", "cherry-pick", or "rewrite history" are missing, so it fits 'good coverage with a few natural terms missing' rather than comprehensive synonym coverage.	4 / 5
Distinctiveness Conflict Risk	Clear niche in git history/commit operations with distinct triggers, and the skip clause actively separates it from generic editing skills; only negligible overlap with commit-message-style skills, so it is not the 'minor overlap risk' anchor.	5 / 5
	Total	19 / 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: code-yeongyu/lazycodex
Path: plugins/omo/skills/git-master/SKILL.md
Commit: 9f97b58

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.