agentleFS
Sign inStart free
emaraschioemaraschio/cursor-commands/.cursor/skill-contracts/commit-same-branch/SKILL.md

commit-same-branch

Skill9 starsChanged 3 months agoMITView on GitHub

Commit on the current branch with conventional message

  • Reads credentials

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Commit changes to the same branch with proper commit message.

    line 8
  2. Distinctive:

    Must use the conventional commit message convention.

    line 13
  3. Distinctive:

    Use a single commit for the changes

    line 17
  4. Distinctive:

    Commit the changes to the branch

    line 18
  5. Distinctive:

    Commit only when the user asks.

    line 34
  6. Distinctive:

    Do not push unless asked; keep commits local until the user requests a push.

    line 35
  7. Distinctive:

    Use the Conventional Commits convention for every message.

    line 36
  8. Distinctive:

    Before staging, review git status, git diff, and recent git log.

    line 37
  9. Distinctive:

    Never print, stage, or commit secrets or credential files (.env, .env.*, keys).

    line 38

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Overview

Commit changes to the same branch with proper commit message.

Steps

  1. Write commit message
    • Must use the conventional commit message convention.
    • Summarize changes clearly
  2. 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 recent git 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free