agentleFS
benororbenoror/obsidianos_work/.agents/skills/commit/SKILL.md

commit

Skill166 starsChanged 5 months agoMITView on GitHub

Stage and commit with flexible intent parsing. Accepts file/folder scope, free-text description, amend, or any combination.

  • Reads credentials

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

Show its rules and text

We split this skill into the rules it gives an agent

15 rules. 0 are common, 11 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 167 edited versions we read keep these.

  • 11

    Distinctive

    This author's own choices. Worth a look.

  • 4

    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. Very specific:

    Amend flag: If the first word is amend, set amend mode and strip it.

    line 26
  2. Distinctive:

    Nothing: No arguments at all — default mode.

    line 29
  3. Distinctive:

    If nothing matches (no changes in scope, or no related files for intent), tell the user and stop.

    line 66
  4. Distinctive:

    If the file set is already fully staged, skip.

    line 70
  5. Very specific:

    If unrelated files are staged, unstage them first (git restore --staged <path>).

    line 71
  6. Distinctive:

    If the user provided intent, use it to guide the message but still ground it in the actual diff.

    line 81
  7. Distinctive:

    Wait for user confirmation before proceeding.

    line 89
  8. Distinctive:

    Before amending, verify ALL of these conditions:

    line 100
  9. Distinctive:

    If any condition fails, refuse and explain why.

    line 106
  10. Very specific:

    When called as part of a sequenced workflow (e.g.

    line 110
  11. Distinctive:

    When committing on behalf of a sequence:

    line 116
  12. Distinctive:

    Always use explicit file paths for staging — never broad patterns.

    line 125
  13. Distinctive:

    If no files were actually modified, skip the commit offer.

    line 126
  14. Very specific:

    Never commit files that likely contain secrets (.env, credentials, tokens).

    line 127
  15. Distinctive:

    When the scope is a folder, include all changed files recursively under it.

    line 128

“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

Usage

CommandWhat it does
/commitCommit staged files; if none staged, infer related changes
/commit <file>Scope to a specific file's changes
/commit <folder>/Scope to a folder's changes
/commit <description>Infer scope from free-text intent
/commit <scope> <description>Scope + explicit intent
/commit amendAmend the last commit (re-use message)
/commit amend <scope/description>Amend with additional scope or new message
(sequence mode)Deferred — sub-skills skip, caller commits once at the end

Argument Parsing

Parse the raw argument string into scope, intent, and flags:

  1. Amend flag: If the first word is amend, set amend mode and strip it. The remainder is parsed normally.
  2. Scope (file or folder): Any token that matches a real path in the repo (file or directory) — whether provided via @-reference or plain text. Multiple scopes are allowed.
  3. Intent (free-text description): Whatever remains after extracting scopes. Used to guide the commit message.
  4. Nothing: No arguments at all — default mode.

Examples:

InputScopeIntentAmend
(empty)——no
Meetings/Engineering/Meetings/Engineering/—no
.gitignore.gitignore—no
my awesome refactor—my awesome refactorno
Meetings/ wrap up notesMeetings/wrap up notesno
amend——yes
amend .obsidian/.obsidian/—yes
amend fixed typo—fixed typoyes

Workflow

1. Gather state

Run in parallel:

  • git diff --staged --stat — staged changes
  • git diff --stat — unstaged changes
  • git status --short — untracked files
  • git log --oneline -5 — recent commits (for style and amend safety)

2. Determine file set

Resolve which files will be committed, based on parsed arguments:

ScenarioFile set
Scope providedOnly changed/untracked files under the given path(s). Ignore everything else.
Intent provided, no scopeAnalyze all changed files; select only those whose diffs relate to the described intent. Present the selection for confirmation.
No args + staged files existUse exactly what's staged. Do NOT add unstaged files — the user intentionally staged those.
No args + nothing stagedAnalyze all changed/untracked files. Group related changes and propose a sensible set. Ask for confirmation.

If nothing matches (no changes in scope, or no related files for intent), tell the user and stop.

3. Stage files

  • If the file set is already fully staged, skip.
  • If unrelated files are staged, unstage them first (git restore --staged <path>).
  • Stage the resolved file set with explicit paths — never broad patterns.

4. Craft the commit message

Analyze the staged diff (git diff --staged) and write:

  • Title: ≤72 chars, conventional format — type: summary.
    • Common types: add (new files), update (modify existing), fix (corrections), chore (config/tooling), feat (new capability), refactor, docs, rename.
  • Body (optional): 1–3 lines explaining "why" if not obvious. Omit for trivial changes.
  • If the user provided intent, use it to guide the message but still ground it in the actual diff.

5. Present and confirm

Show:

  • The list of files that will be committed (or amended).
  • The proposed commit message.

Wait for user confirmation before proceeding.

6. Commit

  • Normal mode: git commit with the confirmed message.
  • Amend mode: git commit --amend (see safety rules below). If the user provided new intent, replace the message; otherwise keep the existing message (--no-edit).

Do not push.

Amend Safety

Before amending, verify ALL of these conditions:

  1. HEAD was created by you in this conversation — check git log -1.
  2. HEAD has not been pushed — git status should show "Your branch is ahead" or the commit should not exist on the remote.
  3. The user explicitly said amend.

If any condition fails, refuse and explain why. Suggest creating a new commit instead.

Sequence Mode

When called as part of a sequenced workflow (e.g. /meeting wrap), the caller owns the commit. Individual sub-skills skip their commit step.

How to detect: the calling workflow explicitly states it is running sub-skills in sequence. Do not offer to commit — just proceed. The sequence owner commits once at the end with a combined message.

Sub-skill commit format

When committing on behalf of a sequence:

  • Message: update: /{workflow-name} {argument} (e.g. update: /meeting wrap Meetings/Engineering/Some Meeting.md).
  • Stage only files modified by the current skill invocation (or full sequence). Use explicit paths.
  • Present and confirm before committing.

Important Notes

  • This workspace may not be a git repo. If git status fails, skip entirely without error.
  • Always use explicit file paths for staging — never broad patterns.
  • If no files were actually modified, skip the commit offer.
  • Never commit files that likely contain secrets (.env, credentials, tokens).
  • When the scope is a folder, include all changed files recursively under it.

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.