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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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-sequenced skill body with concrete commands, formats, and validation checkpoints throughout. It is somewhat verbose for its token budget and monolithic with no reference files, which limits conciseness and progressive disclosure.

Suggestions

Trim motivational prose and the 'Common Rationalizations' table; keep the Red Flags and Verification sections, which already encode the same guidance more tersely.

Split reference-heavy material (git debugging commands, generated-file rules, worktree usage) into files under references/ and link to them from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly actionable, but the motivational Overview prose ('Git is your safety net. Treat commits as save points...'), the DORA aside, and the lengthy 'Common Rationalizations' table are editorial padding that could be trimmed; it does not explain basic concepts Claude lacks, yet is not fully lean.	2 / 3
Actionability	It provides copy-paste-ready git commands (worktree add, tag, bisect, blame), a concrete commit-message format with typed prefixes, branch-naming patterns, a package.json hook config, and worked good/bad examples — fully executable and specific.	3 / 3
Workflow Clarity	Multi-step flows carry explicit validation checkpoints: the Save Point Pattern branches on test pass/fail with a revert fallback, Pre-Commit Hygiene is a sequenced 5-step check, and the Verification section provides checklists for both commits and releases.	3 / 3
Progressive Disclosure	No bundle/reference files exist, so all ~356 lines live in one monolithic SKILL.md; sections are well-organized with clear headers, but content like git-debugging commands, generated-file rules, and worktrees could be split into reference files for a skill this size.	2 / 3
	Total	10 / 12 Passed

Description

92%

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, third-person description with explicit triggers and natural vocabulary covering both workflow and release/versioning concerns. Its main weakness is the catch-all 'making any code change' trigger, which creates conflict risk with adjacent skills.

Suggestions

Drop or narrow 'Use when making any code change' — it is too broad and will cause this skill to surface for tasks better served by sibling skills; rely on the specific git/versioning triggers instead.

Consider consolidating the three 'Use when...' sentences into one to reduce redundancy without losing trigger coverage.

Dimension	Reasoning	Score
Specificity	Beyond the opening 'Structures git workflow practices', the description enumerates many concrete actions — 'committing, branching, resolving conflicts', 'cutting a release, choosing a semantic version bump, tagging, or writing a changelog' — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	It answers both 'what' ('Structures git workflow practices') and 'when' with three explicit 'Use when...' trigger clauses, satisfying the 'clearly answers both what AND when with explicit triggers' anchor.	3 / 3
Trigger Term Quality	Natural developer vocabulary is well covered — 'committing, branching, resolving conflicts', 'parallel streams', 'cutting a release', 'semantic version bump', 'tagging', 'changelog' — terms users would actually say when they need this skill.	3 / 3
Distinctiveness Conflict Risk	The git/versioning triggers are distinct, but 'Use when making any code change' is over-broad and would fire for nearly any code task, overlapping with sibling skills like code-review-and-quality or testing; this matches the 'somewhat specific but could still overlap' anchor rather than a clean niche.	2 / 3
	Total	11 / 12 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
Commit: 70b7506

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