agentleFS
EclipterEclipter/agents/skills/sdlc/commit/SKILL.md

commit

Skill1 starsChanged 6 days agoMITView on GitHub

Create a Git commit or commits.

187 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

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

  • 0

    Common

    Most of the 167 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the calling workflow manages upstream synchronization or history rewriting, follow that workflow's preparation instead.

    line 10
  2. Distinctive:

    If branches have diverged or the local branch is behind upstream and has uncommitted changes, stop and report.

    line 18
  3. Very specific:

    Use commit-message for the message.

    line 27
  4. Very specific:

    Commit. Do not push, amend, or rewrite history unless it's asked explicitly.

    line 30
  5. Very specific:

    If a hook rejects the commit, fix the cause and retry.

    line 31
  6. Distinctive:

    Verify the resulting commit and working tree.

    line 33

“Common” is measured: kept by at least 6 in 10 of the 167 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

Commit

Principles

If the calling workflow manages upstream synchronization or history rewriting, follow that workflow's preparation instead.

Workflow

Prepare

  1. Fetch upstream if configured.
  2. If branches have diverged or the local branch is behind upstream and has uncommitted changes, stop and report.
  3. Fast-forward if behind.

Commit

  1. Inspect git status --short, staged and unstaged diffs, and untracked files. Stage only changes in the requested scope. Preserve unrelated work and its staging state; exclude it from the commit. If the scope is unclear, ask.
  2. Use commit-message for the message. Skip its reply section. For independent changes, stage and commit each atomic change separately, regenerating the message for its actual staged contents.
  3. Commit. Do not push, amend, or rewrite history unless it's asked explicitly. If a hook rejects the commit, fix the cause and retry; never use --no-verify.
  4. Verify the resulting commit and working tree. Report the hash and subject, plus any changes left uncommitted.

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.