Commit changes main

Skill emaraschio/cursor-commands/plugin/.cursor/skill-contracts/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.

What its author says it does

Copied from the file, not written here

Commit directly on main/master when explicitly allowed

SKILL.md

1.2 KB, as published. Nobody here has run it

Overview

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

Steps

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

Commit Message Examples

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

Guardrails

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.

Gives 1 of the 12 instructions most pr commit review skills give

Counted across 888 of the 1,342 authors here whose files we hold, read 2026-08-06

use conventional commits formatin 123 of 888, across 110 files
keep subject line under 72 charactersin 60 of 888, across 46 files
delete branches after mergein 50 of 888, across 37 files
use imperative mood in subject linein 50 of 888, across 41 files
use imperative mood in commit messagesin 45 of 888
generate a conventional commit messagehere, and in 42 of 888
make atomic commitsin 37 of 888, across 25 files
run tests before committingin 36 of 888, across 24 files
run project test suite to verify clean baselinein 35 of 888, across 7 files
run detected project setup commandsin 34 of 888, across 6 files
wrap commit body at 72 charactersin 32 of 888, across 25 files
split unrelated changes into separate commitsin 32 of 888, across 27 files

Said here and by no other author read

ensure all changes are committed correctly
verify changes are up to date with main
commit the changes to the main branch

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.