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.
96
96%
Does it follow best practices?
Impact
93%
1.75xAverage score across 3 eval scenarios
Passed
No known issues
Release process automation
npm run update used
0%
100%
Release notes section at top
100%
100%
Correct version header format
100%
100%
Uses only New/Better/Fix categories
100%
100%
One sentence per bullet
100%
100%
Commit message is 'update: version'
0%
100%
Tag without v prefix
0%
100%
Tag pushed separately
100%
100%
Push to main
40%
100%
Merge main to release branch
0%
0%
Commit message conventions
Format: type colon space desc
100%
100%
Descriptions lowercase
40%
100%
feat for new capability
0%
100%
fix for bug fix
100%
100%
refactor for restructuring
0%
100%
docs for documentation
0%
100%
test for test additions
0%
100%
chore for CI/build
0%
100%
update for incremental improvement
100%
100%
git-log.txt present with 7 commits
100%
100%
Feature branch and connector addition
Connector entry in manifest.json
100%
100%
Correct API base URL in manifest
100%
100%
No custom index.js created
0%
100%
feat branch naming
0%
100%
Branch off main
100%
100%
feat commit type
100%
100%
Commit description lowercase
100%
100%
PR targets main
100%
100%
Test command included
0%
0%
Push to origin
100%
100%
f59d4a2
Table of Contents
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.