Commit same branch
Skill emaraschio/cursor-commands/.cursor/skill-contracts/commit-same-branch
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 commit-same-branchAssembled 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 the current branch with conventional message
SKILL.md
1.2 KB, as published. Nobody here has run it
Overview
Commit changes to the same branch with proper commit message.
Steps
-
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 changes 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
- Commit only when the user asks; do not commit unrequested work.
- Do not push unless asked; keep commits local until the user requests a push.
- Use the Conventional Commits convention for every message.
- Before staging, review
git status,git diff, and recentgit log; write the commit message with a HEREDOC and stay on the current branch (do not create a new branch). - Never print, stage, or commit secrets or credential files (.env, .env.*, keys); exclude them and warn instead.