Commit changes main

Production-grade Cursor slash commands with paired skill contracts, behavioral evals, and ship-gate CI. Install as a user plugin.

Install

npx -y skills add emaraschio/cursor-commands --skill commit-changes-main

Assembled 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.

Copied from the file, not written here

Commit directly on main/master when explicitly allowed

1.2 KB, as published. Nobody here has run it

Commit changes to the main branch of a GitHub repository with proper commit message.

Prepare branch
- Ensure all changes are committed to the correct branch using the conventional commit message convention
- Push changes to remote
- Verify changes are up to date with main
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 main branch
- Push the main branch to the remote repository

feat: add new feature
fix: fix bug
chore: update dependencies
refactor: refactor code
test: add tests
docs: update documentation

Commit to main only with explicit consent; otherwise move the work to a separate branch.
Never force-push main or any shared branch; reconcile with a normal pull or merge instead.
Use the Conventional Commits convention for every message.
Never print, stage, or commit secrets or credential files (.env, .env.*, keys); exclude them and warn instead.