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.
65
78%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/developer-essentials/skills/git-advanced-workflows/SKILL.mdQuality
Discovery
92%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly lists specific advanced Git capabilities and provides explicit trigger guidance via a 'Use when' clause. The main weakness is potential overlap with other Git-related skills, as some trigger terms like 'feature branches' and 'repository issues' could apply to basic Git skills as well. The phrase 'recover from any situation' is slightly hyperbolic but acceptable given the context of reflog and advanced recovery techniques.
Suggestions
Clarify the boundary with basic Git skills by adding a differentiator like 'Use this instead of basic Git skills when the task involves history rewriting, advanced debugging, or multi-worktree setups.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: rebasing, cherry-picking, bisect, worktrees, and reflog. Also mentions concrete outcomes like 'maintain clean history' and 'recover from any situation.' | 3 / 3 |
Completeness | Clearly answers both what ('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'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'rebasing', 'cherry-picking', 'bisect', 'worktrees', 'reflog', 'Git histories', 'feature branches', 'repository issues'. These are terms developers naturally use when seeking help with advanced Git operations. | 3 / 3 |
Distinctiveness Conflict Risk | While it specifies 'advanced' Git workflows, it could overlap with a general Git skill or a basic Git commands skill. The term 'feature branches' and 'repository issues' are broad enough to potentially conflict with simpler Git-related skills. However, the specific mention of advanced operations like bisect, worktrees, and reflog helps differentiate it somewhat. | 2 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid reference-style skill with excellent actionability — every section provides executable commands. However, it's somewhat verbose with explanatory prose Claude doesn't need, and it lacks validation checkpoints for destructive operations like rebasing and force pushing. The reference to 'references/details.md' is unverifiable since no bundle files exist.
Suggestions
Remove explanatory prose like 'Interactive rebase is the Swiss Army knife of Git history editing' and concept definitions Claude already knows — just provide the commands and patterns.
Add explicit validation steps to the rebase and force-push workflows (e.g., 'run tests after rebase, diff against backup branch before force pushing').
Either provide the referenced 'references/details.md' bundle file or remove the reference to avoid a broken link.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary framing ('Swiss Army knife of Git history editing', 'Future you will thank present you') and explains concepts Claude already knows well (what cherry-picking is, what bisect does). The command references themselves are efficient, but the surrounding prose adds unnecessary tokens. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready commands throughout. Every section includes concrete bash commands with clear syntax, flags, and usage patterns. The automated bisect example even specifies exit code conventions. | 3 / 3 |
Workflow Clarity | Git bisect has a clear sequential workflow, and the recovery section is well-organized. However, for destructive operations like interactive rebase and force pushing, there are no explicit validation checkpoints or feedback loops — the 'Test Before Force Push' best practice is mentioned but not integrated into a workflow with verification steps. | 2 / 3 |
Progressive Disclosure | The skill references 'references/details.md' for detailed patterns, but no bundle files are provided, making this reference unverifiable and potentially broken. The main content is fairly long and monolithic — sections like Common Pitfalls, Recovery Commands, and Best Practices could potentially be split out. The single reference is appropriately one-level deep but poorly signaled. | 2 / 3 |
Total | 9 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- wshobson/agents
- Commit
cf6059d
- 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.