CtrlK
BlogDocsLog inGet started
Tessl Logo

git-workflow

Provides expert guidance on Git operations including branch management, commit best practices, merge conflicts, and version control workflows. Use when the user needs help with Git commands, workflows, or resolving repository issues.

64

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./claude/skills/git-workflow/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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-structured, actionable Git reference with executable commands and good organization. Its main weakness is the absence of explicit validation/feedback checkpoints for destructive operations like rebase and force push, which limits workflow clarity.

Suggestions

Add an explicit validation checkpoint before destructive operations, e.g. verify the working tree is clean and run `git rebase --dry-run` style checks before rebasing or force pushing, with a fix-and-retry loop on failure.

Tighten the duplicate guidance between 'Commit Best Practices' and 'Best Practices' (e.g. 'Write meaningful commit messages' repeats the earlier conventional-commit guidance) to improve token efficiency.

Turn the Conflict Resolution prose steps into concrete commands (e.g. `git status`, `git add <file>`, `git rebase --continue`) so every workflow is fully executable.

DimensionReasoningScore

Conciseness

Mostly lean and assumes Claude's Git knowledge, with bullet lists and terse code blocks; minor padding like restating 'Write meaningful commit messages' after already covering commit best practices keeps it just short of a 5.

4 / 5

Actionability

Provides concrete, copy-pasteable commands for the common cases (branch creation, conventional commit, rebase, sync) with only minor gaps such as the conflict-resolution steps being prose rather than full commands.

4 / 5

Workflow Clarity

The 'Conflict Resolution' section lists a sequenced four-step flow, but the skill covers destructive/batch operations (rebase, force push, branch deletion) without an explicit validate-then-proceed feedback loop, which the rubric caps at 3.

3 / 5

Progressive Disclosure

Well-organized into clearly labeled sections (Core Responsibilities, Safety Principles, Common Tasks, Best Practices) with no bundle files present, so all content is appropriately inline for a skill of this size.

4 / 5

Total

15

/

20

Passed

Description

83%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 solid, third-person description that answers both what the skill does and when to use it with concrete Git-domain actions. It is slightly short of fully comprehensive on trigger-term synonyms and action coverage.

DimensionReasoningScore

Specificity

Lists several concrete actions ('branch management', 'commit best practices', 'merge conflicts', 'version control workflows'), giving reasonable coverage of the Git domain with only minor gaps.

4 / 5

Completeness

Clearly states both what the skill does and when to use it ('Use when the user needs help with Git commands, workflows, or resolving repository issues'), matching the anchor for explicit what-and-when coverage.

5 / 5

Trigger Term Quality

Includes natural user-facing terms like 'Git commands', 'workflows', and 'resolving repository issues'; missing common synonyms like 'commit messages' or 'pull requests' as explicit triggers.

4 / 5

Distinctiveness Conflict Risk

The Git-workflow niche is fairly distinct and the triggers are scoped to Git/repository issues, with only minor overlap risk against a generic coding-assistant skill.

4 / 5

Total

17

/

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
einverne/dotfiles
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.