Help the user create properly formatted commit messages and release notes that follow CockroachDB conventions.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versioncommit-helperExecute the skills CLI command in your project's root directory to begin installation:
Fetches commit-helper from cockroachdb/cockroach and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate commit-helper. Access via /commit-helper in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
32.0K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
32.0K
stars
Help the user create properly formatted commit messages and release notes that follow CockroachDB conventions.
git diff --staged or git diff to understand what was modifiedBasic Format:
package: imperative title without period
Detailed explanation of what changed, why it changed, and
how it impacts users. Explain the problem that existed
before and how this commit solves it.
Include context about alternate approaches considered and
any side effects or consequences.
Resolves: #123
Epic: CRDB-357
Release note (category): Description of user-facing change
in past or present tense explaining what changed, how users
can see the change, and why it's important.
Key Requirements:
When to include release notes:
When to exclude release notes:
crdb_internal.Valid Categories:
backward-incompatible change - Breaking changes to stable interfacesenterprise change - Features requiring enterprise licenseops change - Commands/endpoints for operators (logging, metrics, CLI flags)cli change - Commands for developers/contributors (SQL shells, debug tools)sql change - SQL statements, functions, system catalogsui change - DB Console changessecurity update - Security feature changesperformance improvement - Performance enhancementscluster virtualization - Multi-tenancy infrastructurebug fix - Problem fixesgeneral change - Changes that don't fit elsewherebuild change - Source build requirementsDescription guidelines:
Examples:
Good bug fix:
Release note (bug fix): Fixed a bug introduced in v19.2.3 that
caused duplicate rows in CREATE TABLE ... AS results when multiple
nodes attempt to populate the results.
Good feature:
Release note (enterprise change): Shortened the default interval
for the kv.closed_timestamp.target_duration cluster setting from
30s to 3s. This allows follower reads at 4.8 seconds in the past,
a much shorter window than the previous 48 seconds.
Resolves: #123 - Auto-closes issue on PR mergeSee also: #456, #789 - Cross-references issuesEpic: CRDB-357 - Links to epicbackward-incompatible change category for any breaking changesMake data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
commit-helper fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for commit-helper matched our evaluation — installs cleanly and behaves as described in the markdown.
We added commit-helper from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
commit-helper reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend commit-helper for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
commit-helper reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in commit-helper — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
commit-helper reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added commit-helper from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
commit-helper has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 43