git-workflow-and-versioning

Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, 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

76%

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

77%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.

The body is highly actionable with excellent command examples and validation-gated workflows, and its sequencing is clear with feedback loops. It loses points on conciseness (philosophical padding) and progressive disclosure (a long single-file monolith with no reference files splitting out peripheral material).

Suggestions

Trim the conceptual framing (Overview, versioning philosophy, DORA/Hyrum's Law asides) to the minimum needed to justify the practice, since Claude already knows these concepts.

Move peripheral material like 'Using Git for Debugging' and the 'Common Rationalizations' table into a reference file (e.g., references/debugging-and-rationalizations.md) and link to it from the overview.

Consider extracting the release/versioning detail into a separate reference file so SKILL.md stays a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete commands and examples, but narrative framing ('Git is your safety net...', DORA research, Hyrum's Law, the versioning philosophy intro, and the Common Rationalizations table) adds prose Claude largely already knows and could be trimmed.	3 / 5
Actionability	Abundant copy-paste-ready commands and examples — pre-commit hygiene (git diff --staged, grep for secrets, npm test/lint, tsc), worktree setup, git bisect/blame, tag and changelog formats — cover the common cases fully and executably.	5 / 5
Workflow Clarity	Multi-step processes carry explicit validation and feedback loops: the Save Point Pattern (test fails -> revert -> investigate), numbered Pre-Commit Hygiene with test/lint/type checks, and Verification checklists for both commits and releases.	5 / 5
Progressive Disclosure	Sections are well-headed and inline sibling-skill pointers are signaled, but with no bundle files the ~350-line body is monolithic — debugging tips and the rationalizations table are inlined rather than split into reference files.	3 / 5
	Total	16 / 20 Passed

Description

76%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.

The description clearly signals a git-workflow-and-versioning skill with rich, concrete trigger phrases covering both daily git operations and release/versioning work. Its main weaknesses are the generic opening 'what' statement and an overly broad 'any code change' trigger that raises conflict risk.

Suggestions

Replace the generic lead 'Structures git workflow practices' with a concrete enumeration of the core actions (e.g., 'Commits, branches, merges, and resolves conflicts; cuts tagged releases with semver bumps and changelogs').

Narrow the trigger 'Use when making any code change' to git-specific moments to reduce overlap with code-review and testing skills.

Add common synonyms (merge, revert, stash, rebase) to the trigger list for fuller keyword coverage.

Dimension	Reasoning	Score
Specificity	Beyond the generic lead 'Structures git workflow practices', the description enumerates many concrete actions — committing, branching, resolving conflicts, opening/reviewing PRs, pushing, cutting releases, semver bumps, tagging, changelogs — giving comprehensive coverage of both workflow and versioning.	5 / 5
Completeness	Explicit 'Use when...' trigger clauses answer 'when' thoroughly, but the standalone 'what' statement ('Structures git workflow practices') is generic rather than concrete, keeping it just below the top anchor.	4 / 5
Trigger Term Quality	Strong natural terms users would say (commit, branch, conflict, PR, push, release, version bump, tag, changelog) but a few common synonyms like merge, revert, and stash are missing.	4 / 5
Distinctiveness Conflict Risk	The git/versioning niche is distinct, but the broad trigger 'Use when making any code change' overlaps heavily with sibling skills (code review, testing) and could fire for nearly any change.	3 / 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: 48cb116

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