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.
84
74%
Does it follow best practices?
Impact
88%
1.00xAverage score across 6 eval scenarios
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 enumerates specific advanced Git capabilities and provides explicit trigger guidance via a 'Use when' clause. Its 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 description uses proper third-person voice and avoids vague language.
| 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, reflog) and 'when' (explicit '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 with specific operations, 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 skills. | 2 / 3 |
Total | 11 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides highly actionable, executable Git commands covering a comprehensive range of advanced workflows, which is its primary strength. However, it suffers from being a monolithic document that could be better organized with progressive disclosure, and its workflows lack explicit validation checkpoints for destructive operations like force pushes and hard resets. Some verbosity in explanatory text could be trimmed to better respect Claude's existing knowledge of Git concepts.
Suggestions
Split content into multiple files: keep SKILL.md as a concise overview with quick-reference commands, and move detailed workflows to WORKFLOWS.md, advanced techniques to ADVANCED.md, and recovery commands to RECOVERY.md with clear cross-references.
Add explicit validation checkpoints to workflows involving destructive operations, e.g., 'Run tests after rebase and before force push: `npm test`' or 'Verify branch state: `git log --oneline -5`'.
Remove explanatory sentences Claude already knows (e.g., 'Interactive rebase is the Swiss Army knife of Git history editing', 'Binary search through commit history to find the commit that introduced a bug') and let the commands speak for themselves.
Add a feedback loop to the rebase workflow: after conflict resolution, explicitly verify the result with `git diff main` or test suite before proceeding to force push.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured but includes unnecessary explanations Claude already knows (e.g., 'Interactive rebase is the Swiss Army knife of Git history editing', 'Your safety net - tracks all ref movements', explaining what cherry-picking is). The 'When to Use This Skill' section and some descriptive text could be trimmed significantly. However, the core content is mostly command-focused. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready bash commands throughout. Every concept is accompanied by concrete commands with realistic examples, including conflict resolution steps, flags, and variations. The code blocks are real commands, not pseudocode. | 3 / 3 |
Workflow Clarity | The practical workflows are clearly sequenced and numbered, but they lack explicit validation checkpoints. For destructive operations like force pushing, rebasing, and hard resets, there are no 'verify before proceeding' steps or feedback loops (e.g., 'run tests after rebase before force pushing'). The best practices section mentions testing but doesn't integrate it into the workflows themselves. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text at ~300 lines with no references to external files. All content—core concepts, practical workflows, advanced techniques, best practices, pitfalls, and recovery commands—is inlined in a single file. This would benefit significantly from splitting advanced techniques, workflows, and recovery commands into separate referenced files. | 1 / 3 |
Total | 8 / 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
112197c
- 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.