agentleFS
Sign inStart free
epamepam/ketcher/.agents/skills/commit/SKILL.md

commit

Skill927 starsChanged 2 days agoApache-2.0View on GitHub

Stage task changes for user review, then commit them in Ketcher using the canonical issue-derived title after approval. Use when the user invokes /commit or asks to stage and commit current work.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 169 edited versions we read keep these.

  • 5

    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:

    Use this exact format for both the commit subject and PR title:

    line 15
  2. Distinctive:

    Run git status --short --branch and inspect both staged and unstaged diffs, including untracked files relevant to the task.

    line 23
  3. Distinctive:

    If the staged index contains unrelated changes, or file-level staging would include unrelated edits within a mixed file, pause and ask the …

    line 25
  4. Distinctive:

    Wait for explicit user approval.

    line 29
  5. Very specific:

    After approval, create the local commit with the exact title as its subject: git commit -m "#<task number> - <canonical issue title>".

    line 30
  6. Distinctive:

    Do not push, amend, or rewrite history.

    line 31

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

Stage, Review, and Commit Task Changes

Stage only the changes for the current task, ask the user to review the staged diff, and commit only after they explicitly approve. The commit subject must also be the exact PR title format used by this repository.

Title Rule

Use this exact format for both the commit subject and PR title:

#<task number> - <canonical issue title>

Get the task number and canonical title from the issue URL or number supplied by the user or current conversation. If only a number is available and GitHub CLI is installed and authenticated, retrieve the title with gh issue view <number> --json title --jq .title. Do not guess or paraphrase the issue title. If the issue number or canonical title cannot be determined, ask the user before staging or committing.

Procedure

  1. Run git status --short --branch and inspect both staged and unstaged diffs, including untracked files relevant to the task.
  2. Identify which changed files and hunks belong to the current task. Preserve all pre-existing user changes. Do not stage unrelated files or use git add -A as a shortcut.
  3. If the staged index contains unrelated changes, or file-level staging would include unrelated edits within a mixed file, pause and ask the user what to include. Do not reset or discard any changes.
  4. Resolve the issue number and canonical issue title, then construct the exact title #<task number> - <canonical issue title>.
  5. Stage the task-related paths with git add -- <paths>. Review git diff --cached and confirm it contains only the intended changes.
  6. Show the user the staged paths and a concise summary of git diff --cached, and ask them to review the staged changes. Do not commit yet.
  7. Wait for explicit user approval. If the user requests changes, make only the requested changes, stage them, review the updated cached diff, and ask for approval again. Do not commit while approval is pending or ambiguous.
  8. After approval, create the local commit with the exact title as its subject: git commit -m "#<task number> - <canonical issue title>". Do not add a body unless the user asks for one.
  9. Do not push, amend, or rewrite history. If a hook blocks the commit, report the failure and do not bypass the hook.
  10. Report the commit hash, exact subject, and committed paths. State that the same subject is the PR title to use.

Download now (ZIP)

  • Other versions189 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 189

    1. microsoft/vscode★ 194ksame name
    2. TryGhost/Ghost★ 56ksame name
    3. ToolJet/ToolJet★ 41ksame name
    4. ShareX/ShareX★ 41ksame name
    5. openai/symphony★ 27ksame name
    6. ccusage/ccusage★ 19ksame name
    7. ryoppippi/ccusage★ 19ksame name
    8. windmill-labs/windmill★ 18ksame name
    9. EverMind-AI/EverOS★ 14ksame name
    10. EverMind-AI/EverMemOS★ 14ksame name

    179 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use act-on-feedback, add-mcp-tools 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.
    • 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

    • decocmsSkill

      run-local-freestyle

      Run Studio locally with chats and task runs executing in real Freestyle sandboxes, reachable through an ngrok tunnel. Use when asked to "run locally with Freestyle", "test claude-code chats locally", "run the sandbox harness end to end", or to try daemon/harness-runner changes in a real sandbox.

      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

  • In this repository24 other files it gives its agents.

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