CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

git-master

MUST USE for ANY git operations: atomic commits, rebase/squash/fixup, and history search (blame, bisect, log -S, reflog). Load it before running git yourself, or pass load_skills=['git-master'] to the task that commits. Triggers: 'commit', 'rebase', 'squash', 'who wrote', 'when was X added', 'find the commit that'.

Quality

92%

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

The canonical home for this skill is git-master in code-yeongyu/oh-my-openagent

SKILL.md
Quality
Evals
Security

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 exemplary instruction-only skill body: lean, safety-first, and packed with exact commands and validation checkpoints for destructive git operations. The only structural weakness is progressive disclosure — one dangling reference to a non-bundled docs path and a tangential PR-attachment section that slightly dilutes the mode-focused organization.

Suggestions

Verify docs/reference/github-attachment-upload.md actually exists at that path (it is not part of the skill bundle) and consider making it a bundled references/ file so the reference resolves reliably.

Move the PR Body Evidence Attachments section into a separate reference file, keeping SKILL.md focused on the four core modes (COMMIT, REBASE, HISTORY, STATUS).

DimensionReasoningScore

Conciseness

The body is lean and directive throughout with zero concept padding — no explanation of what git or rebase is, just rules like 'Never rebase or rewrite main, master, dev... unless the user explicitly named that exact operation'. Every token earns its place and assumes Claude's competence.

5 / 5

Actionability

Fully executable guidance: a copy-paste bash block of ground-truth commands, exact tool selection per question type (git log -S, git blame -L start,end -- file, git log --follow), and precise recipes like 'git commit --fixup=<hash> followed by GIT_SEQUENCE_EDITOR=: git rebase -i --autosquash <base>'. As an instruction-only skill, its guidance is concrete and specific throughout.

5 / 5

Workflow Clarity

Commit Mode is a numbered 7-step sequence with per-commit validation checkpoints ('Before each commit, verify git diff --staged --stat'), plus a Safety Checks checklist before any write, an explicit recovery path ('use git rebase --abort first. Use reflog only after explaining the recovery path'), and post-rewrite smoke verification — clear sequencing with explicit validation and feedback loops for destructive operations.

5 / 5

Progressive Disclosure

Sections are well-organized by mode with all inline content appropriately placed for a ~100-line skill, and the single external reference ('docs/reference/github-attachment-upload.md') is clearly signaled and one level deep. However, that path does not exist in the skill bundle (no references/ directory), and the PR Body Evidence Attachments section is tangential to the four core modes, leaving minor organization gaps.

4 / 5

Total

19

/

20

Passed

Description

83%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 that explicitly states capabilities with concrete git subcommands and provides an explicit trigger list answering both what and when. Its main weaknesses are a second-person phrase incurring the voice penalty and a trigger list missing a few natural synonyms like 'amend' and 'git history'.

Suggestions

Rewrite 'Load it before running git yourself' in third-person imperative form to avoid the voice penalty (e.g., 'Load before Claude runs git, or pass load_skills=[...]').

Add common trigger synonyms such as 'amend', 'blame', 'git history', and 'undo commit' to the Triggers list.

Narrow 'ANY git operations' slightly (e.g., 'history rewriting and history search') to reduce overlap with adjacent git skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions with specific subcommands ('atomic commits, rebase/squash/fixup, and history search (blame, bisect, log -S, reflog)'), approaching comprehensive coverage. The second-person phrasing 'before running git yourself' triggers the rubric's voice penalty of 1, keeping it below the 5 anchor.

4 / 5

Completeness

Clearly answers both 'what' ('MUST USE for ANY git operations: atomic commits, rebase/squash/fixup, and history search') and 'when' with concrete trigger phrases in an explicit Triggers list, exactly matching the 5 anchor pattern.

5 / 5

Trigger Term Quality

Explicit trigger list ('commit', 'rebase', 'squash', 'who wrote', 'when was X added', 'find the commit that') captures natural user phrasings well. Common variations like 'amend', 'blame', or 'git history' are absent, so it matches 'good keyword coverage; a few natural terms missing' rather than the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

The git-history/rewriting niche is mostly distinct with clear triggers, but 'ANY git operations' plus the generic trigger 'commit' creates minor overlap risk with closely related skills such as commit-message generation or PR-creation skills.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

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.