CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

88

1.32x
Quality

84%

Does it follow best practices?

Impact

93%

1.32x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

76%Weight 40%Scale 1-5

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

A well-organized, highly actionable command reference that assumes Claude's git knowledge. Its weaknesses are the absence of validation/feedback steps for destructive operations (rebase, bisect) and references to ./references files that are not actually bundled.

Suggestions

Add brief validation checkpoints for risky operations, e.g. run tests / `git status` after rebase and confirm `git bisect` result before resetting.

Create the referenced ./references/rebase-patterns.md, stash-patterns.md, and advanced-git.md files, or remove the broken references.

Drop the redundant Quick Reference table or the "When to Use" list to tighten token use, since both duplicate content already present.

DimensionReasoningScore

Conciseness

Body is mostly lean — tables, code blocks, keybinding lists — and does not over-explain what git or lazygit is, but the Quick Reference table repeats commands already shown above and the "When to Use" list duplicates the description's triggers, so it is not fully tight.

4 / 5

Actionability

Throughout it gives copy-paste-ready executable commands (e.g. `gh pr create --title "..."`, `git diff | delta`, `git rebase -i HEAD~N`) and concrete keybindings covering the common cases.

5 / 5

Workflow Clarity

Content is a command catalog with no sequenced multi-step workflows or validation checkpoints, and several operations (rebase, bisect) are risky/destructive; per the rubric cap, destructive operations without validation cannot score above 3.

3 / 5

Progressive Disclosure

Good section structure with clearly signaled one-level-deep references in "Additional Resources", but the three cited ./references/*.md files do not exist in the bundle, a navigation gap that keeps it below the top anchor.

4 / 5

Total

16

/

20

Passed

Description

92%Weight 40%Scale 1-5

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, specific description that names concrete tools and lists many natural trigger phrases, clearly answering both what and when. The only gap is synonym coverage of common git/GitHub terms.

Suggestions

Add common synonyms to the trigger list (e.g., "pull request", "merge", "push", "clone", "branch") to broaden natural-term coverage.

Consider noting the lazygit/gh/delta dependency in the description body itself rather than only in the compatibility field so the trigger surface is self-contained.

DimensionReasoningScore

Specificity

Names the domain ("Enhanced git operations") plus concrete tools (lazygit, gh, delta) and lists many specific actions (stage changes, create PR, review PR, rebase, stash, bisect) — comprehensive coverage matching the top anchor.

5 / 5

Completeness

Explicitly answers both what ("Enhanced git operations using lazygit, gh, and delta") and when ("Triggers on: ...") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

"Triggers on: stage changes, create PR, review PR, check issues, git diff, rebase, stash, bisect" are natural phrases users would say, but common synonyms like "pull request", "merge", "push", "clone", and "branch" are missing, keeping it just below the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

Clear niche of git/GitHub operations with named external tools and git-specific triggers; minimal overlap risk with unrelated skills.

5 / 5

Total

19

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
NeverSight/skills_feed
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.