commit
Generate a commit message and commit staged changes using git.
Works with
Installation Guide
How to use commit on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your machine
- ›Node.js 16+ with npm — verify with
node --version - ›Active project directory where you want to add
commit
Run the install command
Execute the skills CLI command in your project's root directory to begin installation:
Fetches commit from casper-studios/casper-marketplace and configures it for Cursor.
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate commit. Access via /commit in your agent's command palette.
Security Notice
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.
Documentation
Commit
Generate a commit message and commit staged changes using git.
Based on the Conventional Commits v1.0.0 specification.
Guidelines
- Only generate the message for staged files/changes
- Don't add any files using
git add- user decides what to add - DO NOT add any ads or footers
Format
<type>(<scope>): <message title>
<bullet points summarizing what was updated>
Rules
- Title: lowercase, no period, max 50 characters
- Scope: optional, feature affected
- Body: explain why, not just what
- Bullet points: concise and high-level
Allowed Types
| Type | Description |
|---|---|
| feat | New feature |
| fix | Bug fix |
| chore | Maintenance (tooling, deps) |
| docs | Documentation changes |
| refactor | Code restructure (no behavior change) |
| test | Adding or refactoring tests |
| style | Code formatting (no logic change) |
| perf | Performance improvements |
Examples
feat(auth): add JWT login flow
- Implemented JWT token validation logic
- Added documentation for the validation component
fix(ui): handle null pointer in sidebar
refactor(api): split user controller logic
- Extracted validation into separate module
- Simplified error handling flow
Footer (optional)
- Reference issues:
Closes #123 - Breaking changes: Start with
BREAKING CHANGE:
Avoid
- Vague titles: "update", "fix stuff"
- Overly long or unfocused titles
- Excessive detail in bullet points
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases
User Story & Requirements Generation
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
Competitive Analysis
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
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale