git-workflow
Enhanced git operations using lazygit, gh (GitHub CLI), and delta. Triggers on: stage changes, create PR, review PR, check issues, git diff, commit interactively, GitHub operations, rebase, stash, bisect.
77
67%
Does it follow best practices?
Impact
93%
1.32xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/skills-md/0xdarkmatter/claude-mods/git-workflow/SKILL.mdQuality
Discovery
82%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 solid skill description with strong trigger term coverage and clear completeness, explicitly listing both capabilities and trigger conditions. Its main weakness is that the specificity of actions could be improved—listing tool names is helpful but the actual capabilities (e.g., 'interactive staging with lazygit', 'rich diffs with delta') could be more concrete. There's also moderate overlap risk with any basic git skill.
Suggestions
Expand the capability descriptions to be more concrete, e.g., 'Interactive staging and commit workflows via lazygit, rich syntax-highlighted diffs via delta, PR creation and review via gh CLI'
Clarify distinctiveness by specifying when this skill should be chosen over a basic git skill, e.g., 'Use instead of basic git when interactive TUI workflows, GitHub CLI operations, or enhanced diff viewing are needed'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (git operations) and lists tools (lazygit, gh, delta), but the actions listed are mostly brief trigger terms rather than fully described concrete capabilities. It doesn't elaborate on what specific outcomes each action produces. | 2 / 3 |
Completeness | The description answers both 'what' (enhanced git operations using lazygit, gh, and delta) and 'when' (explicit 'Triggers on:' clause listing specific scenarios). The trigger guidance is explicit and detailed. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'stage changes', 'create PR', 'review PR', 'check issues', 'git diff', 'commit interactively', 'GitHub operations', 'rebase', 'stash', 'bisect'. These are terms users would naturally use when requesting these tasks. | 3 / 3 |
Distinctiveness Conflict Risk | While the mention of specific tools (lazygit, gh, delta) helps distinguish it, terms like 'git diff', 'commit', 'rebase', and 'stash' could overlap with a basic git skill. The 'enhanced' qualifier and tool names provide some distinction but not complete clarity on when to choose this over a standard git skill. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
52%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill functions well as a quick-reference cheat sheet with concrete, executable commands for lazygit, gh, and delta. However, it lacks workflow sequencing—there are no multi-step processes with validation checkpoints for operations like rebasing or PR workflows that would benefit from them. The 'When to Use' section adds little value and the quick reference table partially duplicates earlier content.
Suggestions
Replace the 'When to Use' section with at least one concrete multi-step workflow (e.g., a PR creation workflow: branch → commit → push → create PR → verify) with validation checkpoints.
Add a brief rebase workflow with explicit validation steps (e.g., check for conflicts, verify history after rebase) rather than just listing `git rebase -i HEAD~N` as a one-liner.
Remove the quick reference table entries that duplicate commands already shown in detail above, or consolidate into a single reference section to reduce redundancy.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient with useful tables and command references, but the 'When to Use' section is unnecessary filler—Claude already knows when to use git stash or rebase. The quick reference table partially duplicates commands already shown above. | 2 / 3 |
Actionability | Provides concrete, copy-paste ready commands throughout—lazygit keybindings, gh CLI commands with real flags and arguments, delta configuration commands. All examples are executable and specific. | 3 / 3 |
Workflow Clarity | There are no multi-step workflows with sequencing or validation checkpoints. The skill is a reference card of individual commands rather than guided workflows. For operations like rebase, PR creation, or bisect, there's no step-by-step process with verification points. | 1 / 3 |
Progressive Disclosure | References to external files (rebase-patterns.md, stash-patterns.md, advanced-git.md) are well-signaled and one level deep, but no bundle files were provided to verify they exist. The main file includes some content that could be trimmed given those references exist (e.g., the 'When to Use' list). | 2 / 3 |
Total | 8 / 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
- NeverSight/skills_feed
- Commit
2d09b29
- 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.