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 lists specific advanced Git operations and provides explicit trigger guidance via a 'Use when' clause. The main weakness is potential overlap with general Git skills, as some triggers like 'feature branches' and 'repository issues' could match broader Git skills. The description uses proper third-person voice and avoids vague language.
Suggestions
Clarify the boundary with basic Git skills by adding a note like 'Not for basic git add/commit/push/pull operations' to reduce conflict risk.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: rebasing, cherry-picking, bisect, worktrees, reflog, maintaining clean history, and recovering from situations. These are well-defined Git operations. | 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 cover a good range of terms users would naturally use when needing advanced Git help. | 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 skill. The 'collaborating on feature branches' trigger is broad enough to conflict with simpler Git workflow skills. However, the specific advanced operations (bisect, worktrees, reflog) help differentiate it somewhat. | 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.
This skill provides highly actionable, executable Git commands covering a comprehensive range of advanced workflows. However, it suffers from being a monolithic document that could benefit significantly from splitting into focused sub-files, and it lacks explicit validation checkpoints in workflows involving destructive operations like rebasing and force pushing. Some descriptive prose explains concepts Claude already knows well.
Suggestions
Split content into sub-files (e.g., REBASE.md, CHERRY-PICK.md, BISECT.md, RECOVERY.md) and make SKILL.md a concise overview with links to each
Add explicit validation checkpoints to destructive workflows - e.g., 'Run tests before force pushing' as a numbered step, 'Verify conflict resolution with git diff' after rebase --continue
Remove explanatory sentences Claude already knows (e.g., 'Interactive rebase is the Swiss Army knife...', 'Binary search through commit history...', 'Apply specific commits from one branch to another without merging entire branches') to reduce token usage
Trim the 'When to Use This Skill' section - this duplicates what the YAML description already conveys
| 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. At ~300 lines, this could be tightened by ~30-40%. | 2 / 3 |
Actionability | Excellent actionability throughout - every section includes concrete, executable bash commands with realistic examples. Commands are copy-paste ready with specific flags, arguments, and common variations. The practical workflows show complete sequences of real commands. | 3 / 3 |
Workflow Clarity | Multi-step workflows are presented with clear sequences (e.g., bisect workflow, clean up feature branch), but validation checkpoints are largely missing. For destructive operations like force pushing after rebase or interactive rebase, there's no explicit 'verify before proceeding' step. The best practices mention testing but don't integrate verification into the workflows themselves. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text at ~300 lines with no references to external files. Content like the full bisect workflow, worktree details, advanced techniques, and recovery commands could easily be split into separate reference files. Everything is inline with no navigation structure beyond headers. | 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
70444e5
- 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.