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.
82
75%
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
89%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 excellent trigger term coverage and clear 'when to use' guidance via the explicit 'Triggers on:' clause. Its main weakness is that the 'what' portion is somewhat thin—it says 'enhanced git operations' but doesn't elaborate on specific capabilities like interactive staging, PR creation workflows, or diff visualization with delta. The trigger terms compensate well for routing purposes.
Suggestions
Expand the capability description to list specific concrete actions, e.g., 'Performs interactive staging and commits via lazygit, creates and reviews pull requests via gh CLI, and displays enhanced diffs using delta.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (git operations) and lists tools (lazygit, gh, delta), but the actions listed are mostly trigger terms rather than detailed descriptions of concrete capabilities. It doesn't explain what the skill actually does with these tools beyond naming operations. | 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 well-structured. | 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 operations. | 3 / 3 |
Distinctiveness Conflict Risk | The description is clearly scoped to git operations with specific tooling (lazygit, gh CLI, delta), which creates a distinct niche. The trigger terms are specific to git/GitHub workflows and unlikely to conflict with non-git skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
60%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill serves as a solid command reference for git tooling with good actionability and progressive disclosure to reference files. However, it lacks workflow sequencing — there are no multi-step processes showing how to combine these tools for common tasks like 'review and merge a PR' or 'interactive rebase workflow.' The 'When to Use' section adds little value and could be removed to improve conciseness.
Suggestions
Add 1-2 concrete multi-step workflows (e.g., 'PR Review Flow: 1. gh pr checkout 123, 2. git diff main | delta --side-by-side, 3. gh pr review 123 --approve') with validation checkpoints.
Remove the 'When to Use' section entirely — Claude already knows when to use stash, rebase, and bisect.
Consolidate the Quick Reference table with the sections above to eliminate duplication of commands like `lazygit`, `gh pr create`, and `git diff | delta`.
| 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 content already shown in the sections 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 guidance is specific and executable. | 3 / 3 |
Workflow Clarity | There are no multi-step workflows with sequencing or validation checkpoints. The skill is essentially a command reference card with no guidance on how to chain operations together (e.g., stage → commit → create PR flow). For operations like rebase and merge, missing validation/verification steps is a significant gap. | 1 / 3 |
Progressive Disclosure | Clean overview structure with well-organized sections and clear one-level-deep references to detailed pattern files (rebase-patterns.md, stash-patterns.md, advanced-git.md). Content is appropriately split between the overview and reference files. | 3 / 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
- NeverSight/skills_feed
- Commit
f772de4
- 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.