git-master

Git expert combining atomic commits, rebase/squash, and history search (blame, bisect, log -S). Use for any git operations requiring structured commit strategies, history rewriting, or code archaeology. Triggers: 'commit', 'rebase', 'squash', 'who wrote', 'when was X added', 'find the commit that'.

Quality

86%

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

77%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 highly actionable and well-sequenced git workflow with strong validation and recovery loops, but it is verbose due to heavy repetition of the commit-splitting rule and is a single monolithic 1000+ line file that would benefit from splitting the three modes into reference files.

Suggestions

Consolidate the repeated 'multiple commits by default' enforcement into one authoritative section and reference it from later phases instead of restating the rule (and its ALL-CAPS framing) five times.

Split the three modes (COMMIT, REBASE, HISTORY_SEARCH) into separate reference files (e.g. references/commit-mode.md, references/rebase-mode.md, references/history-search.md) and keep SKILL.md as a mode-detection overview that links to them, one level deep.

Remove the leftover '' marker and ensure each phase section is finalized rather than left as a placeholder.

Dimension	Reasoning	Score
Conciseness	The body is mostly actionable, but the 'split into multiple commits' rule is restated many times (CORE PRINCIPLE, MANDATORY SELF-CHECK, Phase 3.0/3.5, FINAL CHECK, Anti-Patterns) with heavy ALL-CAPS enforcement that could be consolidated, placing it at 'mostly efficient but could be tightened'.	3 / 5
Actionability	It provides copy-paste-ready git commands, detection regexes, and concrete examples across all three modes (e.g. 'git log -S "searchString" --oneline', 'GIT_SEQUENCE_EDITOR=: git rebase -i --autosquash $MERGE_BASE'), covering the common cases fully.	5 / 5
Workflow Clarity	Multi-step processes are clearly sequenced into numbered phases with explicit validation checkpoints and feedback loops for destructive operations (rebase --abort, reflog recovery, --force-with-lease warnings, bisect reset, a blocking FINAL CHECK checklist).	5 / 5
Progressive Disclosure	The file is internally well-structured with mode-detection routing and phase headers, but at ~1013 lines everything is inlined in one monolithic SKILL.md with no bundle files and no references — the three modes clearly could be split into separate files, and a leftover '<!-- PLACEHOLDER_PHASE2 -->' marker signals incomplete organization.	3 / 5
	Total	16 / 20 Passed

Description

95%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 well-crafted description in third-person voice that explicitly covers both capability and trigger conditions with natural user phrases. It is comprehensive and clearly distinguishable, with only minor gaps in enumerating every sub-capability.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'atomic commits, rebase/squash, and history search (blame, bisect, log -S)' — but leaves a few specializations (conflict resolution, branch cleanup) implicit, so minor gaps in coverage keep it just below the comprehensive anchor.	4 / 5
Completeness	It clearly states what ('Git expert combining atomic commits, rebase/squash, and history search') and when ('Use for any git operations requiring structured commit strategies, history rewriting, or code archaeology' plus concrete triggers), explicitly answering both with trigger phrases.	5 / 5
Trigger Term Quality	The explicit 'Triggers' list ('commit', 'rebase', 'squash', 'who wrote', 'when was X added', 'find the commit that') covers natural phrasings and synonyms a user would actually say, matching the comprehensive-coverage anchor.	5 / 5
Distinctiveness Conflict Risk	The niche is clearly scoped to advanced git operations with distinct trigger phrases, so overlap with other skills is minimal and unlikely to fire for the wrong skill.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (1014 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: ArabelaTso/Skills-4-SE
Path: skills/git-master/SKILL.md
Commit: 4f38503

Reviewed: 23 hours 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.