jbvc/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.
82
82%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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. Its main weakness is potential overlap with other Git-related skills, as 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, along with concrete goals 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. | 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 mention of 'feature branches' and 'repository issues' is broad enough to potentially conflict with simpler Git-related skills. | 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 comprehensive Git advanced workflows skill with excellent actionability—every technique includes executable commands and realistic examples. However, it suffers from verbosity and redundancy (concepts explained twice in different sections), lacks validation checkpoints in destructive workflows, and could benefit from moving detailed content into referenced files rather than keeping everything inline.
Suggestions
Remove redundancy between Core Concepts and Practical Workflows sections—either consolidate or move detailed examples to referenced files, keeping only the most essential commands inline.
Add explicit validation checkpoints to destructive workflows (e.g., 'Run tests before force pushing', 'Verify rebase result with git log --oneline before proceeding').
Trim explanatory prose that Claude already knows (e.g., descriptions of what cherry-picking or bisect are) and remove the 'Do not use this skill when' section which adds no actionable value.
Move the detailed Advanced Techniques and Recovery Commands sections to referenced files and link them inline where relevant, reducing the main file to a focused overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive 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'). The 'Do not use this skill when' section adds no value. Several sections could be tightened, and there's significant redundancy between Core Concepts and Practical Workflows (e.g., bisect is explained twice with similar examples). | 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 handling, flags, and variations. The code examples are complete and directly usable. | 3 / 3 |
Workflow Clarity | The practical workflows are clearly sequenced with numbered steps, but validation checkpoints are largely missing. For destructive operations like force pushing and history rewriting, there are no explicit 'verify before proceeding' steps. The rebase workflow lacks a validation step between rebasing and force pushing. Best practices mention testing but don't integrate verification into the workflows themselves. | 2 / 3 |
Progressive Disclosure | The skill references external files (references/, assets/, scripts/) at the bottom, which is good, but the main file itself is very long (~300 lines) with content that could be split out. The Core Concepts section duplicates much of what's in the Practical Workflows section. The references are listed but not clearly signaled inline where they'd be most useful. | 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.
Reviewed
Table of Contents