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.
81
67%
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 capabilities and provides explicit trigger guidance via a 'Use when' clause. The main weakness is potential overlap with general Git skills, as some trigger terms like 'feature branches' and 'repository issues' could apply to basic Git usage 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
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides comprehensive, executable Git command examples covering advanced workflows, which is its primary strength. However, it is far too verbose for a Claude skill — it explains concepts Claude already knows, includes motivational commentary, and dumps everything into a single monolithic file. The lack of validation checkpoints in destructive workflows (rebase + force push, cherry-pick across releases) and the absence of progressive disclosure significantly reduce its effectiveness as a skill document.
Suggestions
Remove all explanatory prose that describes what Git features are (e.g., 'Cherry-picking applies specific commits...', 'Your safety net - tracks all ref movements') — Claude already knows these concepts. Keep only the actionable commands and workflow sequences.
Add explicit validation steps to destructive workflows: e.g., 'Run tests after rebase before force pushing', 'Verify cherry-picked commit compiles/passes on target branch before moving to next release branch'.
Split content into multiple files: keep SKILL.md as a concise overview with quick-reference commands, and move detailed workflows to WORKFLOWS.md, recovery commands to RECOVERY.md, and best practices to PRACTICES.md with clear cross-references.
Remove the 'Common Pitfalls' and 'Best Practices' bullet lists that state obvious Git knowledge, or condense them into a 3-line 'Critical reminders' section with only non-obvious guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Significantly verbose for a Claude skill. Explains basic Git concepts Claude already knows (what cherry-picking is, what bisect does, what worktrees are). Includes extensive commentary like 'Interactive rebase is the Swiss Army knife of Git history editing' and 'Future you will thank present you.' The core concepts section largely duplicates man page content. Best practices like 'Atomic Commits: Each commit should be a single logical change' teach nothing new to Claude. | 1 / 3 |
Actionability | All examples are concrete, executable bash commands with realistic scenarios. Commands are copy-paste ready with clear flags and arguments. Workflows show complete sequences including conflict handling and cleanup steps. | 3 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with numbered steps and logical ordering. However, validation checkpoints are largely missing — for example, the 'Clean Up Feature Branch Before PR' workflow doesn't include verifying the rebase result before force pushing, and the cherry-pick workflow doesn't validate that the cherry-picked commit works on the target branch. For destructive operations like force push and rebase, explicit validation/verification steps are absent. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text at ~300+ lines with no references to external files. All content is inline — the advanced techniques, recovery commands, best practices, and common pitfalls could easily be split into separate reference files. There are no cross-references or navigation aids beyond section headers. | 1 / 3 |
Total | 7 / 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
27a7ed9
- 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.