A skill for creating properly formatted Git commit messages following the Conventional Commits specification.
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 charon-fan/agent-playbook 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
27
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
27
stars
A skill for creating properly formatted Git commit messages following the Conventional Commits specification.
This skill activates when you:
<type>(<scope>): <subject>
<body>
<footer>
| Type | Description |
|---|---|
feat |
A new feature |
fix |
A bug fix |
docs |
Documentation only changes |
style |
Changes that do not affect the meaning of the code (formatting, etc.) |
refactor |
A code change that neither fixes a bug nor adds a feature |
perf |
A code change that improves performance |
test |
Adding missing tests or correcting existing tests |
chore |
Changes to the build process or auxiliary tools |
ci |
Changes to CI configuration files and scripts |
build |
Changes that affect the build system or external dependencies |
The scope should indicate the area of the codebase affected:
components, hooks, store, styles, utilsapi, models, services, database, authci, deploy, dockerCloses #123, Fixes #456, Refs #789Closes #123, #456, #789BREAKING CHANGE: followed by descriptionfeat(auth): add OAuth2 login support
Implement OAuth2 authentication flow to allow users to log in
with their Google or GitHub accounts.
This change adds:
- New OAuth2 middleware for handling callbacks
- Updated login UI with social login buttons
- User profile synchronization
Closes #123
fix(api): resolve race condition in user creation
The concurrent user creation requests could result in duplicate
email entries. Added unique constraint and proper error handling.
Fixes #456
refactor(user): simplify profile update logic
Extracted common validation logic into a reusable function
to reduce code duplication across profile update endpoints.
docs: update API documentation with new endpoints
Added documentation for the v2 user management endpoints
including request/response examples and error codes.
updated stuff # Too vague, no type/scope
fixed bug # No context about which bug
feat: added feature # Redundant ("feat" means new feature)
Feat(User): Add Login # Incorrect capitalization
feat: A really really really long subject line that exceeds the recommended limit # Too long
When introducing breaking changes, add BREAKING CHANGE: to the footer:
feat(api): migrate to REST v2
The API endpoints have been restructured for better consistency.
Old endpoints are deprecated and will be removed in v3.0.
BREAKING CHANGE: `/api/v1/users` is now `/api/v2/users`.
All consumers must update their integration by 2025-03-01.
When writing a commit message:
git diff to understand what changedUse the validation script to check commit message format:
python scripts/validate_commit.py "your commit message"
references/conventional-commits.md for full specificationreferences/examples.md for more examplesreferences/scopes.md for recommended scope namingMake 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
We added commit-helper from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
I recommend commit-helper for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: commit-helper is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in commit-helper — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
commit-helper fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
commit-helper is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for commit-helper matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: commit-helper is focused, and the summary matches what you get after install.
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.
showing 1-10 of 64