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 capabilities and includes an explicit 'Use when' clause with relevant trigger scenarios. The 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 'feature branches' and 'repository issues' triggers are somewhat broad and could 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 Git advanced workflows skill with strong actionability—every technique includes executable commands and realistic scenarios. However, it suffers from being overly long and monolithic, with redundancy between core concepts and practical workflows sections. The lack of explicit validation checkpoints in destructive workflows (rebase, force push) is a notable gap for a skill covering risky Git operations.
Suggestions
Add explicit validation/verification steps within workflows (e.g., 'Run tests before force pushing', 'Verify rebase result with git log --oneline before continuing') to create proper feedback loops for destructive operations.
Move detailed reference content (Advanced Techniques, Recovery Commands, Common Pitfalls) into separate referenced files, keeping SKILL.md as a concise overview with quick-start examples and navigation links.
Eliminate redundancy between 'Core Concepts' and 'Practical Workflows'—either consolidate into workflow-first format or keep concepts as a brief reference table with workflows as the primary content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary explanations (e.g., 'Interactive rebase is the Swiss Army knife of Git history editing', 'Your safety net - tracks all ref movements'), and the 'When to Use This Skill' section is verbose. However, most content is practical commands and examples. The overall length (~300 lines) is excessive for what could be more tightly organized, with significant overlap between 'Core Concepts' and 'Practical Workflows' sections. | 2 / 3 |
Actionability | The skill provides fully executable bash commands throughout, with concrete examples for every technique. Commands are copy-paste ready with realistic scenarios (e.g., cherry-picking hotfixes to release branches, automated bisect with test scripts, split commit workflow). | 3 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced (numbered workflows 1-5), but validation checkpoints are largely missing. For destructive operations like force pushing after rebase or interactive rebase, there's no explicit 'verify/test before proceeding' step embedded in the workflows. The best practices mention testing but don't integrate verification into the workflow steps themselves. | 2 / 3 |
Progressive Disclosure | The skill references external files at the end (references/, assets/, scripts/) which is good, but the main file itself is a monolithic wall of content. The core concepts section duplicates much of what appears in the practical workflows. Content like 'Advanced Techniques', 'Common Pitfalls', and 'Recovery Commands' could be split into separate reference files with the SKILL.md serving as a concise overview. | 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
6e3d68c
- 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.