git-workflow-release

Standardized process for committing changes and releasing a new version. Includes steps for bumping versions in package files, updating the CHANGELOG.md, ensuring the README.md is up to date, and creating git release tags. Use when the user asks to "prepare a release", "bump the version", or "release a new version".

Quality

86%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

72%

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

This is a solid release process skill with clear sequential steps and actionable commands. Its main weaknesses are the inclusion of some explanatory content Claude already knows (SemVer definitions) and the lack of explicit validation/verification checkpoints between steps, particularly after version bumping and after pushing. The workflow is well-structured but could benefit from feedback loops to catch errors.

Suggestions

Remove the SemVer definitions (MAJOR/MINOR/PATCH explanations) since Claude already knows these — just reference 'following SemVer'.

Add a validation step after version bumping (e.g., 'Verify the version was updated in all files: grep -r "<OLD_VERSION>" to ensure no stale references remain') and after pushing (e.g., verify the tag exists on remote).

Dimension	Reasoning	Score
Conciseness	Mostly efficient but includes some unnecessary explanation. The SemVer definitions (MAJOR/MINOR/PATCH) are well-known to Claude and don't need spelling out. The CHANGELOG categorization list and some phrasing could be tightened, but overall it's not excessively verbose.	2 / 3
Actionability	Provides concrete, executable git commands for committing, tagging, and pushing. Includes specific commit message format, npm version command, and tag creation syntax that are copy-paste ready. The changelog format example is specific and actionable.	3 / 3
Workflow Clarity	Steps are clearly sequenced and logically ordered, but there are no explicit validation checkpoints or feedback loops. For instance, after bumping the version there's no step to verify the version was updated correctly across all files, and there's no verification after pushing. The 'ensure all tests pass' step in step 1 lacks a re-verification after changes are made.	2 / 3
Progressive Disclosure	For a standalone skill with no bundle files, the content is well-organized into clearly labeled sections with a logical progression. The edge cases section is appropriately separated at the end. The skill is under 80 lines and doesn't need external references for its scope.	3 / 3
	Total	10 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong skill description that clearly articulates specific actions (version bumping, changelog updates, release tagging), provides explicit trigger guidance with natural user phrases, and occupies a distinct niche. It follows the recommended pattern of listing capabilities followed by a 'Use when' clause with concrete examples.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: bumping versions in package files, updating CHANGELOG.md, ensuring README.md is up to date, and creating git release tags.	3 / 3
Completeness	Clearly answers both 'what' (standardized process for committing changes and releasing, with specific steps listed) and 'when' (explicit 'Use when' clause with three concrete trigger phrases).	3 / 3
Trigger Term Quality	Includes natural trigger phrases users would actually say: 'prepare a release', 'bump the version', 'release a new version'. Also contains relevant keywords like 'CHANGELOG', 'version', 'release tags', and 'git'.	3 / 3
Distinctiveness Conflict Risk	Clearly scoped to the release/versioning workflow niche. The specific mention of version bumping, CHANGELOG, release tags, and the trigger phrases make it unlikely to conflict with general git or documentation skills.	3 / 3
	Total	12 / 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: ucdavis/ai-skills-registry
Commit: c0b2e4b

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