git-workflow-and-versioning

Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump, tagging, or writing a changelog.

Quality

73%

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-and-versioning/SKILL.md

Quality

Content

71%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 highly actionable, well-structured git workflow skill with strong examples and validation checkpoints. It is let down by verbosity in framing/diagrams and by being a single long file with no progressive disclosure.

Suggestions

Trim philosophical framing, redundant ASCII diagrams, and the 'Common Rationalizations' table to tighten conciseness; keep the concrete commands and templates.

Split the Release & Versioning section into a separate reference file (e.g. references/VERSIONING.md) linked from a brief overview block, giving the skill one-level-deep progressive disclosure.

Add a single end-to-end workflow (branch → commit slices → validate → merge → tag → changelog) that ties the existing patterns into one sequenced checklist.

Dimension	Reasoning	Score
Conciseness	Core guidance is concrete and efficient, but the body is padded with philosophical framing ("Git is your safety net..."), multiple ASCII diagrams, and a "Common Rationalizations" table that could be trimmed without losing actionable value.	3 / 5
Actionability	Fully executable, copy-paste-ready commands and templates cover the common cases: `git tag -a`, `git bisect`, `git worktree add`, commit-message format with types, .gitignore snippet, lint-staged config, and a changelog template.	5 / 5
Workflow Clarity	Clear sequences with feedback loops (the Save Point Pattern: Test passes → Commit / Test fails → Revert → Investigate) and validation checklists (Pre-Commit Hygiene, Verification); slightly loose because it is a collection of patterns rather than one end-to-end workflow.	4 / 5
Progressive Disclosure	Well-organized with clear section headers, but it is a monolithic ~350-line single file with no bundle files and no one-level-deep references; the release/versioning section and rationalizations table are candidates to split out.	3 / 5
	Total	15 / 20 Passed

Description

75%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, trigger-rich description that clearly names its niche and provides abundant explicit "Use when" guidance. Its main weakness is the generic lead verb and one over-broad trigger.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions ("committing, branching, resolving conflicts... cutting a release, choosing a semantic version bump, tagging, or writing a changelog") but leads with the generic verb "Structures git workflow practices," which keeps it just below comprehensive.	4 / 5
Completeness	Both "what" ("Structures git workflow practices") and "when" (three explicit "Use when..." clauses with concrete triggers) are present; the generic "what" phrasing prevents a 5.	4 / 5
Trigger Term Quality	Strong natural terms users would say (committing, branching, resolving conflicts, release, version bump, tagging, changelog); a few common variants (merge, pull request, gitignore) are missing, so it is not quite comprehensive.	4 / 5
Distinctiveness Conflict Risk	Clear git/versioning niche with distinct triggers, but "Use when making any code change" is broad and creates minor overlap with closely related code-change skills.	4 / 5
	Total	16 / 20 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: addyosmani/agent-skills
Path: skills/git-workflow-and-versioning/SKILL.md
Commit: df1edb2

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