agentleFS
Sign inStart free
emaraschioemaraschio/cursor-commands/.cursor/skill-contracts/commit-changes-main/SKILL.md

commit-changes-main

Skill9 starsChanged 3 months agoMITView on GitHub

Commit directly on main/master when explicitly allowed

  • Reads credentials

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    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 main branch of a GitHub repository with proper commit message.

    line 8
  2. Distinctive:

    Ensure all changes are committed to the correct branch using the conventional commit message convention

    line 13
  3. Distinctive:

    Verify changes are up to date with main

    line 15
  4. Distinctive:

    Must use the conventional commit message convention.

    line 18
  5. Distinctive:

    Use a single commit for the changes

    line 22
  6. Distinctive:

    Commit the changes to the main branch

    line 23
  7. Distinctive:

    Commit to main only with explicit consent.

    line 39
  8. Distinctive:

    Never force-push main or any shared branch.

    line 40
  9. Distinctive:

    Use the Conventional Commits convention for every message.

    line 41
  10. Distinctive:

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

    line 42

≈ “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 main branch of a GitHub repository with proper commit message.

Steps

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

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