Commit
Skill emaraschio/cursor-commands/.cursor/skill-contracts/commit
Production-grade Cursor slash commands with paired skill contracts, behavioral evals, and ship-gate CI. Install as a user plugin.
npx -y skills add emaraschio/cursor-commands --skill commitAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 9 stars9 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Commit on a new branch with conventional message
SKILL.md
1.2 KB, as published. Nobody here has run it
Overview
Commit changes to the repository in a new branch with proper commit message.
Steps
-
Prepare branch
- Create a new branch
- Verify branch is up to date with main or master
-
Write commit message
- Must use the conventional commit message convention.
- Summarize changes clearly
-
Commit changes
- Use a single commit for the changes
- Commit the changes to the branch
- Push the branch to the remote repository
Commit Message Examples
feat(scope): add new feature
fix(script): resolve script error
chore(script): update script dependencies
refactor(script): standardize script error handling
test(script): add comprehensive script tests
docs(script): update script documentation
Guardrails
- Use the Conventional Commits convention for every message.
- Commit only when the user asks; do not push or amend without an explicit request.
- Never skip hooks; if a hook fails, fix the issue and make a new commit.
- Never print, stage, or commit secrets or credential files (.env, .env.*, keys); exclude them and warn instead.