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
78%
Does it follow best practices?
Impact
96%
1.09xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./tests/ext_conformance/artifacts/agents-wshobson/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. Its 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, 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 the advanced Git vocabulary users would naturally use. | 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 workflow skill. The terms 'feature branches' and 'repository issues' are broad enough to potentially conflict with simpler Git 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 and highly actionable Git advanced workflows skill with excellent executable examples throughout. Its main weaknesses are verbosity (explanatory text Claude doesn't need, overly long inline content that could be split into referenced files) and missing validation checkpoints in workflows involving destructive operations like force-pushing and rebasing. The skill would benefit from being trimmed to an overview with references to detailed guides.
Suggestions
Add explicit validation steps to destructive workflows (e.g., 'git log --oneline to verify rebase result before force pushing', 'run tests after cherry-pick to confirm no regressions')
Move detailed sections like 'Advanced Techniques', 'Common Pitfalls', and 'Recovery Commands' into the referenced files (e.g., references/git-rebase-guide.md) and keep only a concise overview in SKILL.md
Remove explanatory phrases Claude already knows (e.g., 'Swiss Army knife of Git history editing', 'Apply specific commits from one branch to another without merging entire branches') to reduce token usage
| 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 - nearly every section includes concrete, executable bash commands with realistic examples. Commands are copy-paste ready with specific flags, arguments, and realistic branch/commit references. The practical workflows show complete sequences of real commands. | 3 / 3 |
Workflow Clarity | The practical workflows show clear sequences of commands, but most lack explicit validation checkpoints. For example, Workflow 1 (clean up before PR) doesn't include a 'verify the rebase result' step, and Workflow 2 (hotfix to multiple releases) doesn't verify the cherry-pick succeeded on each branch. The rebase workflow mentions handling conflicts but doesn't have a proper validate-then-proceed feedback loop. Given these are potentially destructive operations (force push, rebase), missing validation caps this at 2. | 2 / 3 |
Progressive Disclosure | The Resources section at the end references external files (references/, assets/, scripts/) which is good progressive disclosure structure. However, the main body is quite long and monolithic - the 'Advanced Techniques' section and detailed workflows could be split into referenced files. The core SKILL.md tries to cover too much inline rather than providing an overview with pointers. | 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
- Dicklesworthstone/pi_agent_rust
- Commit
47823e3
- 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.