agentleFS
Sign inStart free
aymericbeaumetaymericbeaumet/dotfiles/.agents/skills/commit/SKILL.md

commit

Skill22 starsChanged 2 months agoMITView on GitHub

Stage all changes and create a Conventional Commit without pushing. Use when the user asks to commit all current changes.

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, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 168 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Stage all changes: Run git add -A to stage everything (tracked and untracked).

    line 18
  2. Very specific:

    Commit: Create the commit. Do NOT amend an existing commit.

    line 22

“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

Task

  1. Capture the source work: Inspect the current branch, HEAD, upstream, index, complete tracked diff, and untracked files before changing directories. The request refers to this checkout's changes, including its existing local commits.
  2. Require a bonsai worktree unless the repository's AGENTS.md designates direct work on its default branch, in which case stay in the current checkout and skip this step. Otherwise follow the bonsai skill's existing-work handoff. When creating a task branch, base it on the captured source HEAD and copy the intended pending changes without altering their originals. Verify the destination contains the complete intended changes and no unrelated additions before staging. Continue there without waiting for confirmation.
  3. Stage all changes: Run git add -A to stage everything (tracked and untracked).
  4. Generate a commit message: Analyze the staged diff (git diff --cached) and recent commit history. The message MUST follow the latest published Conventional Commits specification: <type>[optional scope][optional !]: <description>, followed by an optional body and optional footers separated by blank lines. Use feat for a feature and fix for a bug fix. Mark a breaking change with ! before : or a BREAKING CHANGE: footer. Other types such as build, chore, ci, docs, style, refactor, perf, and test are allowed when they accurately describe the change. Keep the first line under 72 characters. Add a body only if the change is non-trivial. If the user's request includes commit-message guidance, use it as guidance, but still write and validate the message yourself.
  5. Commit: Create the commit. Do NOT amend an existing commit. Do NOT use --no-verify. Do NOT push.

Report the commit message, number of files changed, and worktree path. If work was copied from another checkout, state that its original pending changes remain there.

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