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

78%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/git-advanced-workflows/SKILL.md

Quality

Content

65%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.

The body is highly actionable with comprehensive executable commands, but it is held back by redundancy between its two major technique sections, generic boilerplate, missing validation checkpoints on destructive workflows, and a Resources section whose referenced bundle files do not exist.

Suggestions

Merge the redundant 'Core Concepts' and 'Practical Workflows' sections and remove the generic 'Instructions' and 'Do not use this skill when' boilerplate to tighten conciseness.

Add explicit validation checkpoints to destructive workflows — e.g. insert a test/verify step between `git rebase -i main` and `git push --force-with-lease`, and verify recovered state after `git reset --hard` in the recovery workflow.

Create the referenced bundle files (references/git-rebase-guide.md, references/git-conflict-resolution.md, references/git-history-rewriting.md, assets/git-workflow-checklist.md, assets/git-aliases.md, scripts/git-clean-branches.sh) or remove the broken references so navigation is functional.

Dimension	Reasoning	Score
Conciseness	The bulk is concrete commands, but there is a generic boilerplate 'Instructions' section ('Clarify goals, constraints, and required inputs...'), a filler 'Do not use this skill when' section, and substantial redundancy between 'Core Concepts' and 'Practical Workflows' which re-cover the same five techniques.	3 / 5
Actionability	Dense with copy-paste-ready, executable git commands for every technique (rebase, cherry-pick, bisect, worktree, reflog) and end-to-end workflows covering the common cases.	5 / 5
Workflow Clarity	Workflows are sequenced but lack explicit validation checkpoints for destructive operations — e.g. Workflow 1 force-pushes after rebase with no test/verify step, and Workflow 5 recovers via reset --hard with no verification; per the rubric, missing validation on destructive/batch operations caps this dimension at 3.	3 / 5
Progressive Disclosure	A '## Resources' section clearly signals one-level-deep references, but all six referenced files (references/.md, assets/.md, scripts/*.sh) do not exist — navigation is broken — and substantial detail that belongs in those separate files is instead inlined across the ~400-line monolithic body.	3 / 5
	Total	14 / 20 Passed

Description

92%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 clearly states both capabilities and trigger conditions with concrete technique names. The only minor gap is trigger-term synonym coverage, which keeps it just short of a perfect score on that dimension.

Dimension	Reasoning	Score
Specificity	Names five concrete techniques — 'rebasing, cherry-picking, bisect, worktrees, and reflog' — plus two concrete goals ('maintain clean history and recover from any situation'), giving comprehensive coverage of specific actions rather than vague language.	5 / 5
Completeness	Explicitly answers both 'what' ('Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog...') and 'when' ('Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural trigger phrases like 'complex Git histories', 'collaborating on feature branches', and 'troubleshooting repository issues' alongside the technique names, but misses common variations users might say such as 'merge conflicts', 'lost commits', or 'undo a commit'.	4 / 5
Distinctiveness Conflict Risk	The 'advanced Git workflows' niche with named high-level techniques (bisect, worktrees, reflog) is clearly distinct from basic git skills and unlikely to trigger 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
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: 3eff4af

Reviewed: 1 day 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.