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

78%

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

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 thorough, highly actionable Git standards body with strong progressive disclosure via real reference files. It loses points for missing validation/feedback loops on destructive operations and for some redundant and padding sections.

Suggestions

Add explicit validation/verification checkpoints to destructive workflows (e.g., run git status / tests after reset --hard, merge, or rebase) to lift workflow_clarity above the destructive-ops cap of 3.

Remove the redundant 'Best Practices Summary' and 'Summary' sections, or fold them into the sections they repeat, to reduce token padding.

Create the referenced examples/commit-messages.txt and examples/workflow-commands.sh files, or remove those references, so all signaled links resolve to real bundle files.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with tables and code, but the redundant 'Best Practices Summary' and 'Summary' sections plus an inlined PR template add padding that could be trimmed.	3 / 5
Actionability	Extensive copy-paste-ready bash commands and concrete workflow examples cover the common cases fully.	5 / 5
Workflow Clarity	Workflows are clearly sequenced, but destructive and batch operations (reset --hard, rebase, merge) lack explicit validation checkpoints or feedback loops, which caps this dimension at 3 per the rubric.	3 / 5
Progressive Disclosure	A clear overview with seven well-signaled one-level-deep references to real files; however the referenced examples/ files do not exist and the closing Summary repeats earlier content.	4 / 5
	Total	15 / 20 Passed

Description

87%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, trigger-rich description that explicitly states both what the skill does and when to use it using natural user phrasing. Minor specificity and keyword-coverage gaps keep it just below a perfect ceiling on two dimensions.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('create git commit', 'manage branches', 'use Conventional Commits', 'handle merge conflicts') with only minor coverage gaps, fitting the 'several specific actions' anchor.	4 / 5
Completeness	Explicitly answers 'when' via 'should be used when the user asks to...' with concrete triggers and 'what' via 'Provides comprehensive Git workflow guidance for team collaboration'.	5 / 5
Trigger Term Quality	Quoted natural phrases users would say plus synonyms ('git workflow', 'Conventional Commits', 'pull request workflows') give good coverage, though a few natural variations are missing.	4 / 5
Distinctiveness Conflict Risk	Targets a clear Git-workflow niche with distinct triggers, giving minimal conflict risk with other skills.	5 / 5
	Total	18 / 20 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: 6ed46da

Reviewed: 7 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.