CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

78

Quality

98%

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

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.

A tightly written, highly actionable skill body that sequences destructive git operations with explicit validation checkpoints and recovery paths. Progressive disclosure is good but slightly hampered by a tangential attachment section referencing a non-bundled file.

Suggestions

Move the "PR Body Evidence Attachments" section into a separate reference file or a more clearly scoped sub-skill, since it is unrelated to the core commit/rebase/history workflow.

Either bundle the referenced `docs/reference/github-attachment-upload.md` or drop the reference so the body has no dangling pointer.

Consider a short "Quick reference" table mapping each Mode Gate value to its primary command(s) for faster lookup.

DimensionReasoningScore

Conciseness

Lean and directive throughout — no re-explanation of git concepts Claude already knows; every line instructs an action or states a constraint, with no padding.

5 / 5

Actionability

Provides copy-paste-ready commands for every mode (e.g. `git commit --fixup=<hash>`, `GIT_SEQUENCE_EDITOR=: git rebase -i --autosquash <base>`, `git log -S "text"`) covering the common cases concretely.

5 / 5

Workflow Clarity

Commit Mode is a numbered 1–7 sequence with explicit verification checkpoints ("Before each commit, verify git diff --staged --stat", "After each commit, verify git log -1 --oneline"), plus Safety Checks checklists and a rebase-abort feedback loop for destructive history rewrites.

5 / 5

Progressive Disclosure

Well-organized into clear mode-based sections with one clearly signaled one-level reference (`docs/reference/github-attachment-upload.md`); the PR-attachment aside is tangential to the core git-history purpose and the referenced file is not present in the bundle.

4 / 5

Total

19

/

20

Passed

Description

100%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, specific description that concretely enumerates capabilities, gives natural trigger phrases, and sets a clear use/non-use boundary. It is concise without padding.

DimensionReasoningScore

Specificity

Lists many concrete actions — "atomic commits, staging, commit-message style, rebase, squash, fixup/autosquash, blame, bisect, reflog, git log -S/-G" — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both "what" (the listed git operations) and "when" ("MUST USE whenever a task needs a commit or git-history investigation"), plus a negative boundary ("Do not use for ordinary code edits unless...").

5 / 5

Trigger Term Quality

Includes natural phrases users actually say — "who wrote this", "when was this added", "commit", "rebase", "blame", "bisect" — covering the common entry points to git-history work.

5 / 5

Distinctiveness Conflict Risk

Clear git-history niche with distinct triggers and an explicit exclusion clause for ordinary code edits, keeping conflict risk with general coding skills minimal.

5 / 5

Total

20

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
code-yeongyu/lazycodex
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.