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.

1.32x

Quality

—

Does it follow best practices?

Impact

93%

1.32x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Content

45%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-stocked, actionable git/gh/lazygit command reference, but it is a flat cheat-sheet rather than a set of workflows and its promised reference files do not exist. Strongest on actionability; weakest on workflow sequencing and progressive disclosure.

Suggestions

Add sequenced workflows with validation checkpoints for destructive and multi-step operations — e.g., rebase (confirm a clean tree, rebase, resolve conflicts, force-push with --force-with-lease) and bisect (start, mark good/bad, end/reset) — rather than presenting them as single commands.

Create the referenced `./references/rebase-patterns.md`, `stash-patterns.md`, and `advanced-git.md` files (the `references/` directory is absent) or remove the 'Additional Resources' section so navigation is not a dead end.

Reduce redundancy by consolidating the Tools table, Quick Reference table, and 'When to Use' section, which restate the same commands and triggers.

Dimension	Reasoning	Score
Conciseness	The body is a mostly efficient command reference that avoids explaining concepts Claude already knows, but the Tools table, Quick Reference table, and 'When to Use' section duplicate the same commands and triggers, so it could be tightened.	2 / 3
Actionability	It provides concrete, copy-paste-ready commands throughout (e.g., `gh pr create --title "..." --body "..."`, `git diff \| delta --side-by-side`, `git stash push -m "msg"`), with no pseudocode and no missing key details for a reference cheat-sheet.	3 / 3
Workflow Clarity	No multi-step process is sequenced: destructive ops like `gh pr merge --squash` and history-rewriting `git rebase -i` get no validation checkpoints, and inherently multi-step ops like `git bisect start` appear as a single unexplained line.	1 / 3
Progressive Disclosure	The 'Additional Resources' section signals three one-level-deep references (`./references/rebase-patterns.md`, `stash-patterns.md`, `advanced-git.md`), but the `references/` directory does not exist, so the disclosure chain is broken and the detailed content is unreachable.	1 / 3
	Total	7 / 12 Passed

Description

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.

A strong, third-person description with an explicit trigger clause and a rich list of concrete, natural-sounding actions. Its only real weakness is moderate overlap with a generic git skill via the plain git verbs in its triggers.

Dimension	Reasoning	Score
Specificity	It lists many concrete actions — 'stage changes, create PR, review PR, check issues, git diff, commit interactively, GitHub operations, rebase, stash, bisect' — alongside the named tools lazygit, gh, and delta, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	It states what the skill does ('Enhanced git operations using lazygit, gh, and delta') and explicitly when to use it via a 'Triggers on:' clause, answering both what and when with explicit triggers.	3 / 3
Trigger Term Quality	Phrases like 'stage changes', 'create PR', 'review PR', 'git diff', 'rebase', 'stash', and 'bisect' are natural terms a user would say when needing this skill, giving good coverage well above the thin score-2 example.	3 / 3
Distinctiveness Conflict Risk	The lazygit/gh/delta framing and PR/issue triggers carve a niche, but generic git verbs in the trigger list ('git diff', 'commit', 'rebase', 'stash', 'bisect') would overlap with a plain git-operations skill.	2 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: NeverSight/skills_feed
Commit: 26d37ce

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.