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.
Install with Tessl CLI
npx tessl i github:wshobson/agents --skill git-advanced-workflows87
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillAgent success when using this skill
Validation for skill structure
Discovery
100%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 articulates specific advanced Git capabilities, includes natural trigger terms developers would use, and explicitly states both what the skill does and when to use it. The description uses proper third-person voice and distinguishes itself from basic Git operations through specific advanced terminology.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'rebasing, cherry-picking, bisect, worktrees, and reflog' along with 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, and reflog') and when ('Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'Git', 'rebasing', 'cherry-picking', 'bisect', 'worktrees', 'reflog', 'feature branches', 'repository issues' - these are terms developers naturally use when seeking help with advanced Git operations. | 3 / 3 |
Distinctiveness Conflict Risk | Focuses specifically on 'advanced' Git workflows with distinct technical terms (bisect, worktrees, reflog) that differentiate it from basic Git skills; unlikely to conflict with general version control or basic commit/push skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%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 and good progressive structure. The main weaknesses are some verbosity in explanations Claude doesn't need and missing explicit validation checkpoints in workflows involving destructive operations like force pushing and history rewriting.
Suggestions
Remove conceptual explanations Claude already knows (e.g., 'Interactive rebase is the Swiss Army knife...', 'Your safety net - tracks all ref movements') and trim the 'When to Use' section
Add explicit validation steps to workflows - e.g., 'Verify with git log --oneline before force pushing' or 'Run tests after rebase completes, before continuing'
Integrate the 'Best Practices' safety checks directly into the relevant workflows rather than listing them separately
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but includes some unnecessary explanations Claude would know (e.g., 'Interactive rebase is the Swiss Army knife of Git history editing', explaining what worktrees do conceptually). The 'When to Use This Skill' section is somewhat redundant given the description. | 2 / 3 |
Actionability | Excellent executable code examples throughout - all bash commands are copy-paste ready with realistic scenarios. The practical workflows section provides complete, step-by-step command sequences for common tasks. | 3 / 3 |
Workflow Clarity | Workflows are clearly sequenced with numbered steps, but validation checkpoints are mostly implicit. For risky operations like force pushing and rebasing, there's no explicit 'verify before proceeding' step - just best practices mentioned separately. The recovery section helps but isn't integrated into workflows. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from core concepts to practical workflows to advanced techniques. References to additional resources are clearly signaled at the end with one-level-deep links to specific topics. | 3 / 3 |
Total | 10 / 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
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.