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

80%

Does it follow best practices?

Impact

93%

1.75x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.cursor/skills/git-workflow/SKILL.md

Quality

Content

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

Highly actionable and token-efficient single-file guide with concrete commands and real paths. The main weakness is the release workflow, which sequences clearly but omits an explicit validation checkpoint before tagging an irreversible release.

Suggestions

Add an explicit validation step to the Release Process (e.g., 'Run npm test and confirm it passes before tagging') so the destructive release flow has a checkpoint, which would lift workflow_clarity above 3.

Tighten the Commit Messages section by trimming the 'quick fix / quick patch' aside and the duplicated connector commit-scope examples to improve conciseness.

Consider moving the Connector-Specific Notes or the full commit-example list into a referenced file if the guide grows, to preserve the lean overview pattern.

Dimension	Reasoning	Score
Conciseness	Mostly lean with tables and concrete examples that assume Claude's git knowledge; minor padding such as the 'quick fix' aside and connector commit examples could be trimmed, keeping it below 5.	4 / 5
Actionability	Provides copy-paste-ready commands with real file paths ('npm run update', 'git tag 1.7.19', 'npm test', 'src/connectors/manifest.json') covering the common commit, branch, release, and test cases.	5 / 5
Workflow Clarity	The release process is a clear numbered sequence (update version, release notes, commit, tag/push) but lacks an explicit validation checkpoint before the irreversible tag-and-release step; the destructive-operation cap at 3 applies even though local test commands exist in a separate section.	3 / 5
Progressive Disclosure	A single, well-sectioned file with clear headers and tables; no external references are needed at this scale, so it sits at 'good structure' rather than the reference-split 5 anchor.	4 / 5
	Total	16 / 20 Passed

Description

83%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 well-crafted description that clearly states both what it covers and when to use it, with concrete trigger phrases and a distinct project-scoped niche. Minor room for improvement in action specificity and synonym coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and lists four concrete coverage areas ('commit message conventions, branching strategy, release process, and version bumping'); falls short of 5 because these are topic areas rather than granular concrete actions.	4 / 5
Completeness	Explicitly states what the guide covers and follows with a concrete 'Use when ...' trigger clause enumerating specific situations, matching the 5 anchor.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('committing changes', 'creating branches', 'cutting releases', 'updating release notes') but lacks synonyms or the variety that would warrant a 5.	4 / 5
Distinctiveness Conflict Risk	Scoped to a named monorepo ('rc-unified-crm-extension') with project-specific conventions, giving a clear niche with only minor overlap risk against a generic git skill.	4 / 5
	Total	17 / 20 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
Path: .cursor/skills/git-workflow/SKILL.md
Commit: ca1742e

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.