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

commit

Skill9 starsChanged 3 months agoMITView on GitHub

Commit on a new branch with conventional message

  • Reads credentials

188 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use validate-plan, act-on-feedback and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • shawn-dumasSkill

    validate-plan

    Validate an orchestration plan after pre-flight certification. Runs adversarial review, deep review (verify prompt data against codebase), and PoC gate for risky approaches. Auto-invoked by orchestrate-* skills at Step 8.

    Also in 5 projects that use this

  • MicrosoftSkill

    act-on-feedback

    Act on user feedback attached to the current session. Use when the user submits feedback on the session's changes via the Submit Feedback button.

    Also in 3 projects that use this

  • decocmsSkill

    add-mcp-tools

    Guide for adding new MCP tools with consistent patterns for schemas, tool definitions, registry updates, and Better Auth integration

    Also in 3 projects that use this

  • MicrosoftSkill

    generate-run-commands

    Generate or modify run commands for the current session. Use when the user wants to set up or update run commands that appear in the session's Run button.

    Also in 3 projects that use this

  • mitsuhikoSkill

    oebb-scotty

    Austrian rail travel planner (ÖBB Scotty). Use when planning train journeys in Austria, checking departures/arrivals at stations, or looking for service disruptions. Covers ÖBB trains, S-Bahn, regional trains, and connections to neighboring countries.

    Also in 3 projects that use this

  • mitsuhikoSkill

    pi-share

    Load and parse session transcripts from shittycodingagent.ai/buildwithpi.ai/buildwithpi.com/pi.dev (pi-share) URLs. Fetches gists, decodes embedded session data, and extracts conversation history.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 168 edited versions we read keep these.

  • 10

    Distinctive

    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 repository in a new branch with proper commit message.

    line 8
  2. Distinctive:

    Create a new branch

    line 13
  3. Distinctive:

    Verify branch is up to date with main or master

    line 14
  4. Distinctive:

    Must use the conventional commit message convention.

    line 17
  5. Distinctive:

    Use a single commit for the changes

    line 21
  6. Distinctive:

    Commit the changes to the branch

    line 22
  7. Distinctive:

    Use the Conventional Commits convention for every message.

    line 38
  8. Distinctive:

    Commit only when the user asks.

    line 39
  9. Distinctive:

    Never skip hooks; if a hook fails, fix the issue and make a new commit.

    line 40
  10. Distinctive:

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

    line 41

“Common” is measured: kept by at least 6 in 10 of the 168 edited versions of this file we could read. “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 repository in a new branch with proper commit message.

Steps

  1. Prepare branch
    • Create a new branch
    • Verify branch is up to date with main or master
  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 branch
    • Push the branch 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

  • Use the Conventional Commits convention for every message.
  • Commit only when the user asks; do not push or amend without an explicit request.
  • Never skip hooks; if a hook fails, fix the issue and make a new commit.
  • 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