agentleFS
Sign inStart free
rpraharajrpraharaj/ai-sdlc/skills/commit/SKILL.md

commit

Skill0 starsChanged 15 days agoMITView on GitHub

Create a git commit from the real working tree diff. Match this repository's commit-message style. Use when the user wants to commit or check in changes. Do not push unless asked. Do not commit secrets or unrelated files.

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

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

  • 0

    Common

    Most of the 168 edited versions we read keep these.

  • 2

    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
  1. Distinctive:

    Create one honest commit from what is actually in the tree.

    line 17
  2. Distinctive:

    Commit everything when the tree mixes unrelated changes (do not silently bundle)

    line 34

“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

Commit

Create one honest commit from what is actually in the tree. Do not push unless asked.

Is this the right skill?

SignalDo this instead
Open a PRcommit first if needed, then open-pr
Undorevert-change
Not a git repostop

Required inputs

  • A non-empty diff that belongs to the request
  • git

Human decisions (do not invent)

  • Commit everything when the tree mixes unrelated changes (do not silently bundle)
  • --no-verify (only if they explicitly asked)
  • Amend (only if they asked and the commit is yours and not on a shared remote)

Procedure

  1. Inspect: git status, git diff, git diff --cached, git log -8 --oneline.
  2. Load engineering-bar Secret files. Any match → stop.
  3. Stage only files that belong to the request. Do not git add . unless they asked to commit all remaining changes and the secret check passed.
  4. Message matches git log style. Subject = what changed and why from the diff. No invented files. Do not mention agents or “generated by.”
  5. Non-interactive commit. If hooks fail, fix the cause.

Output

  • Path: the new commit
  • Template: references/commit-report.md

Quality bar

  • Secrets absent
  • Unrelated files left unstaged and listed
  • Did not push unless asked

Done

Fill the report. If they also asked for a PR, open-pr.

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