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' 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 skill selection 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/GitHub operations with specific tooling (lazygit, gh CLI, delta), making it highly distinguishable from general coding skills or other version control approaches. The trigger terms are specific to this domain. | 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 provides a solid, well-organized reference card for git tooling with concrete commands and good progressive disclosure to reference files. However, it lacks actual workflow sequences for multi-step operations like rebasing, bisecting, or PR review flows—these are entirely deferred to reference files, leaving the main skill as just a command cheat sheet. The 'When to Use' section adds no value for Claude.
Suggestions
Add at least one multi-step workflow with validation (e.g., interactive rebase: create backup branch → rebase → verify → force push) rather than deferring all workflows to reference files.
Remove the 'When to Use' section—Claude already understands when to use git stash, rebase, or bisect.
Remove or consolidate the quick reference table, which largely duplicates commands already shown in the tool-specific sections above it.
| 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. Every tool section includes executable bash commands with real flags and arguments, and the quick reference table gives specific commands for each task. | 3 / 3 |
Workflow Clarity | There are no multi-step workflows defined—just isolated commands listed by tool. For a skill covering rebase, bisect, and PR creation (multi-step operations), there's no sequencing, no validation checkpoints, and no error recovery guidance. The actual workflow patterns are deferred entirely to reference files. | 1 / 3 |
Progressive Disclosure | Clean overview structure with well-organized sections by tool, a quick reference summary, and clearly signaled one-level-deep references to detailed pattern files for rebase, stash, and advanced git operations. | 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
e437c3c
- 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.