git-workflow

This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team collaboration.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/git-workflow/SKILL.md

Quality

Content

65%

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

Highly actionable command examples and clear workflow sequencing, but undermined by verbosity (restating basic Git knowledge), missing validation checkpoints on destructive operations, and broken example-file references.

Suggestions

Remove or move foundational Git knowledge Claude already has (basic .gitignore patterns, SemVer definitions, standard stash/blame/revert usage) into the reference files to tighten the body.

Add explicit validation/verification checkpoints (e.g., run CI/tests before merging, confirm a tag exists after release) to the destructive and batch workflows.

Fix or remove the broken references to examples/commit-messages.txt and examples/workflow-commands.sh, which do not exist in the bundle.

Dimension	Reasoning	Score
Conciseness	The ~470-line body restates foundational Git knowledge Claude already has (basic .gitignore patterns, SemVer MAJOR/MINOR/PATCH definitions, standard stash/blame/revert usage) and ends with a Summary rehashing earlier sections; it is mostly efficient but could be tightened significantly.	2 / 3
Actionability	Provides many copy-paste-ready, fully executable command sequences (daily dev, hotfix, release workflows), a PR template, conflict-marker examples, and concrete tag operations — clearly above the pseudocode 2-anchor.	3 / 3
Workflow Clarity	Daily/hotfix/release workflows are clearly numbered and sequenced, but destructive/batch operations (git reset --hard, git push -d, merge --no-ff, rebases) lack explicit validation checkpoints or validate→fix→retry feedback loops, capping this at 2 per the rubric.	2 / 3
Progressive Disclosure	Seven references/*.md files are real and well-signaled inline and in a Reference Files section, but the body also points to an examples/ directory (commit-messages.txt, workflow-commands.sh) that does not exist, and the inline content duplicates much of what lives in the references.	2 / 3
	Total	9 / 12 Passed

Description

90%

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 description with explicit when-triggers and good natural keyword coverage; its only weakness is a slightly vague, padded capability statement ('comprehensive guidance for team collaboration') rather than a sharp list of concrete actions.

Dimension	Reasoning	Score
Specificity	The description names the Git-workflow domain and several concrete actions ('create git commit', 'manage branches', 'handle merge conflicts'), but the capability statement 'Provides comprehensive Git workflow guidance for team collaboration' is somewhat high-level and padded rather than a crisp list of concrete actions like the 3-anchor.	2 / 3
Completeness	Explicitly answers both what ('Provides comprehensive Git workflow guidance for team collaboration') and when ('This skill should be used when the user asks to...'), satisfying the explicit-trigger requirement that would otherwise cap this at 2.	3 / 3
Trigger Term Quality	Strong, natural coverage of terms users would say: 'create git commit', 'manage branches', 'use Conventional Commits', 'handle merge conflicts', 'git branching strategies', 'pull request workflows'.	3 / 3
Distinctiveness Conflict Risk	The Git-workflow / Conventional Commits / branching / PR niche is distinct with specific triggers unlikely to fire for unrelated skills, clearly above the generic 2-anchor.	3 / 3
	Total	11 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: Galaxy-Dawn/claude-scholar
Path: skills/git-workflow/SKILL.md
Commit: 2f7766f

Reviewed: about 13 hours 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.