git-workflow

Git workflow guide for the rc-unified-crm-extension monorepo. Covers commit message conventions, branching strategy, release process, and version bumping. Use when committing changes, creating branches, cutting releases, updating release notes, or asking about the project's Git conventions.

1.75x

Quality

—

Does it follow best practices?

Impact

93%

1.75x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

100%

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

A tight, actionable Git workflow reference that assumes Claude's competence and delivers copy-paste commands, clear numbered release steps, and a validation checkpoint. Organization is clean and self-contained with no unnecessary nesting.

Dimension	Reasoning	Score
Conciseness	Lean throughout: tables for commit types and branches, copy-paste commands, and no exposition of git concepts Claude already knows — every section earns its tokens.	3 / 3
Actionability	Provides fully executable, specific commands (npm run update, git checkout -b feat/<name>, git tag <version>, npm test) plus concrete commit-message examples drawn from the repo.	3 / 3
Workflow Clarity	Release process is a clearly numbered four-step sequence, and the CI/CD section adds an explicit validation checkpoint ("Before pushing, run tests locally" with commands) before the consequential tag/push step.	3 / 3
Progressive Disclosure	No bundle files exist; the guide is a single self-contained SKILL.md organized into clearly labeled sections (Project Context, Commits, Branching, Release, CI/CD, Connectors) with no nested references.	3 / 3
	Total	12 / 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.

A well-crafted description that names concrete capabilities, uses third-person voice, and provides an explicit trigger clause with natural user terms. It is clearly scoped to a single monorepo, minimizing conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — "commit message conventions, branching strategy, release process, and version bumping" — each a distinct, specific action area rather than vague language.	3 / 3
Completeness	Explicitly states both what it does (Git workflow guide covering conventions/branching/release/versioning) and when to use it via an explicit "Use when..." trigger clause.	3 / 3
Trigger Term Quality	The "Use when committing changes, creating branches, cutting releases, updating release notes, or asking about the project's Git conventions" clause covers natural phrases a user would actually say.	3 / 3
Distinctiveness Conflict Risk	Scoped to the specific rc-unified-crm-extension monorepo with distinct, repo-specific triggers, making it unlikely to fire for unrelated git skills.	3 / 3
	Total	12 / 12 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
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: ringcentral/rc-unified-crm-extension
Commit: 25fc4c6

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