git-advanced-workflows

Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.

Quality

82%

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

65%Weight 40%Scale 1-3

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

The content is highly actionable with thorough executable Git examples, but it is verbose with conceptual padding and duplication, omits inline validation checkpoints for destructive operations, and references bundle files that are absent.

Suggestions

Trim conceptual explanations Claude already knows (e.g. definitions of bisect/reflog/rebase) and de-duplicate the repeated bisect instructions to improve token efficiency.

Add explicit validation checkpoints inside destructive workflows (e.g. 'run tests / verify build' before 'git push --force-with-lease' and a verification step after 'git reset --hard') to lift workflow clarity.

Either create the referenced references/, scripts/, and assets/ files and move detail into them, or remove the dangling Resources pointers so progressive disclosure is honest.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable examples, but explains concepts Claude already knows ('Interactive rebase is the Swiss Army knife', 'Binary search through commit history to find the bug', reflog as 'Your safety net') and repeats material (bisect appears in three sections), so it could be tightened.	2 / 3
Actionability	Concrete, executable bash commands throughout (e.g. 'git rebase -i HEAD~5', 'git cherry-pick abc123..def456', 'git worktree add -b bugfix/urgent ../project-hotfix main') are copy-paste ready with specific flags and examples.	3 / 3
Workflow Clarity	Workflows are sequenced, but destructive/batch operations (force-with-lease push in Workflow 1, reset --hard in Workflow 5) lack inline validation checkpoints; per the rubric this caps workflow clarity at 2.	2 / 3
Progressive Disclosure	A Resources section signals referenced files, but the references/, scripts/, and assets/ directories do not exist (dangling pointers), and the bulk of detail lives inline rather than being split into those files, so structure is only partially realized.	2 / 3
	Total	9 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it names specific capabilities, includes an explicit 'Use when' trigger clause covering both what and when, and is clearly distinct from other skills. Voice is appropriately action-oriented.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete techniques ('rebasing, cherry-picking, bisect, worktrees, and reflog') plus concrete goals ('maintain clean history and recover from any situation'), matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	It explicitly answers both 'what' (master advanced Git workflows including the named techniques) and 'when' (an explicit 'Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues' clause).	3 / 3
Trigger Term Quality	The 'Use when' clause surfaces natural terms users would say ('feature branches', 'troubleshooting repository issues', 'complex Git histories'), giving good coverage of plausible trigger phrasings.	3 / 3
Distinctiveness Conflict Risk	The description carves a clear niche around advanced Git workflows with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 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
referenced_paths_exist	Referenced path issues: 6 missing	Warning

	Total	15 / 16 Passed

Repository: rmyndharis/antigravity-skills
Path: skills/git-advanced-workflows/SKILL.md
Commit: e63f7dd

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