agentleFS
osmlabosmlab/name-suggestion-index/.claude/skills/commit/SKILL.md

commit

Skill893 starsChanged yesterdayBSD-3-ClauseView on GitHub

Stage and commit all changes in this repo

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

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

  • 0

    Common

    Most of the 167 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the user passed an argument, it can hold commit details, instructions, or both:

    line 10
  2. Distinctive:

    Do the following steps in order:

    line 14
  3. Distinctive:

    Run git status to see what's modified

    line 16
  4. Very specific:

    Run git add -A to stage everything (.gitignore already excludes transient runtime files)

    line 17
  5. Distinctive:

    If there is nothing to stage, say so clearly and stop — do not create an empty commit

    line 18
  6. Very specific:

    Write a commit message that summarizes the recent work to a temp file, then run git commit -F <tempfile> and delete the temp file afterward.

    line 19
  7. Distinctive:

    Do NOT use git commit -m — multi-line messages with special characters break shell quoting.

    line 20
  8. Very specific:

    Do NOT use heredoc syntax (<< 'EOF') — it interacts badly with some agents' terminal tools.

    line 21
  9. Very specific:

    Instead, use printf to write the temp file, one 'line' argument per line:

    line 22
  10. Very specific:

    If commit details were provided (e.g.

    line 28
  11. Very specific:

    Only push if the user asked to (e.g.

    line 32

“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

You are performing a git commit for this repo.

If the user passed an argument, it can hold commit details, instructions, or both:

  • Commit details (e.g. closes #123) go in the commit message, as described in step 4.
  • Instructions (e.g. and push, only the README changes) are for you to follow. Don't put them in the commit message.

Do the following steps in order:

  1. Run git status to see what's modified
  2. Run git add -A to stage everything (.gitignore already excludes transient runtime files)
  3. If there is nothing to stage, say so clearly and stop — do not create an empty commit
  4. Write a commit message that summarizes the recent work to a temp file, then run git commit -F <tempfile> and delete the temp file afterward.
    • Do NOT use git commit -m — multi-line messages with special characters break shell quoting.
    • Do NOT use heredoc syntax (<< 'EOF') — it interacts badly with some agents' terminal tools.
    • Instead, use printf to write the temp file, one 'line' argument per line:
      printf '%s\n' 'First line' '' 'Second line' 'Third line' > /tmp/commitmsg.txt
      git commit -F /tmp/commitmsg.txt
      rm -f /tmp/commitmsg.txt
    • If commit details were provided (e.g. closes #123), include them on their own line after the first line (subject), separated by a blank line:
      printf '%s\n' 'First line' '' 'closes #123' > /tmp/commitmsg.txt
  5. Only push if the user asked to (e.g. /commit and push). Otherwise stop after committing, so the user can review or amend the commit first.

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.