git-master

MUST USE whenever a task needs a commit or git-history investigation. Covers atomic commits, staging, commit-message style, rebase, squash, fixup/autosquash, blame, bisect, reflog, git log -S/-G, and questions like who wrote this or when was this added. Do not use for ordinary code edits unless the user asks for git work.

Quality

96%

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

92%

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

The body is lean, highly actionable, and clearly sequenced with validation checkpoints for risky history operations. The main weakness is a broken reference to a non-existent attachment-upload doc, which slightly undermines navigation.

Suggestions

Remove or fix the reference to docs/reference/github-attachment-upload.md, which does not exist in the bundle — either create the referenced file or inline the small amount of guidance needed.

If attachment upload is a rare edge case, move it out of the main flow entirely (e.g., behind an explicit optional subsection) so the core git-history workflow stays uncluttered.

Dimension	Reasoning	Score
Conciseness	Lean throughout — short imperative rules and a tight parallel 'Ground Truth' command block — with no explanation of git concepts Claude already knows; not below because every section earns its place without padding.	3 / 3
Actionability	Provides copy-paste-ready commands ('git status --short', 'git commit --fixup=<hash>', 'GIT_SEQUENCE_EDITOR=: git rebase -i --autosquash <base>') and concrete per-mode steps; not below because the guidance is executable rather than descriptive or pseudocode.	3 / 3
Workflow Clarity	Commit Mode lays out a numbered 7-step sequence with verification checkpoints ('verify git diff --staged --stat', 'verify git log -1 --oneline') and a dedicated Safety Checks list with recovery paths ('rebase --abort', reflog); not below because validation and feedback loops are explicit for these destructive/batch operations.	3 / 3
Progressive Disclosure	Sections are well-organized with no bundle files to split, but the body references 'docs/reference/github-attachment-upload.md' which does not exist — a dead/one-level reference that is not clearly resolvable; not 3 because the reference is broken, and not 1 because the rest is well structured rather than a monolithic wall.	2 / 3
	Total	11 / 12 Passed

Description

100%

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 precise, well-scoped description that names concrete capabilities, natural trigger phrasings, explicit when-to-use guidance, and a clear anti-trigger. It avoids fluff and over-claims.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions — 'atomic commits, staging, commit-message style, rebase, squash, fixup/autosquash, blame, bisect, reflog, git log -S/-G' — matching the 'lists multiple specific concrete actions' anchor; not below because it is comprehensive rather than naming only some actions.	3 / 3
Completeness	Explicitly answers both what ('Covers atomic commits, staging...') and when ('MUST USE whenever a task needs a commit or git-history investigation'), plus an explicit anti-trigger; not below because the 'when' is stated, not merely implied.	3 / 3
Trigger Term Quality	Includes natural user phrasings like 'a task needs a commit', 'git-history investigation', and 'who wrote this or when was this added', giving good coverage of terms users would actually say; not below because it spans both imperative and investigative triggers.	3 / 3
Distinctiveness Conflict Risk	Niche is clearly git history/commit work and it actively excludes conflicts via 'Do not use for ordinary code edits unless the user asks for git work'; not below because the boundary is explicit, reducing overlap with general code-edit skills.	3 / 3
	Total	12 / 12 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: 895b70c

Reviewed: 4 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.