agentleFS
Sign inStart free
dagonetdagonet/claude-code-toolkit/skills/commit/SKILL.md

commit

Skill4 starsChanged 7 months agoMITView on GitHub

Stage and commit changes with native git, after showing the user exactly what will be committed. Triggers on /cct:commit.

  • Reads credentials

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

10 rules. 0 are common, 7 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 168 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If there are no changes, tell the user and stop

    line 15
  2. Very specific:

    If .claude/template-manifest.json exists in the repo root:

    line 33
  3. Very specific:

    If any files have status PROJECT_CUSTOM or CONFLICT, append after the commit: "Template drift detected: X file(s) modified locally.

    line 35
  4. Very specific:

    If any files have status AUTO_UPDATE, append after the commit: "Template updates available for X file(s).

    line 36
  5. Distinctive:

    If no manifest exists or template-sync-tools MCP is unavailable: skip silently

    line 37
  6. Distinctive:

    Before reporting the commit as done, confirm each of these:

    line 44
  7. Distinctive:

    MUST NOT commit without showing the user what will be committed

    line 54
  8. Distinctive:

    MUST NOT include files the user didn't intend to commit

    line 55
  9. Distinctive:

    If unsure which files to include, ASK the user

    line 56
  10. Distinctive:

    All manifest operations use MCP template-sync-tools — do NOT read/modify the manifest manually

    line 58

“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

Execute a proper commit workflow using native git (PR1 removed the MCP-git mandate — the guard hooks gate git rather than ban it).

Workflow

  1. Check status
    • git status --short
    • If there are no changes, tell the user and stop
  2. Review changes
    • git diff --stat for unstaged changes
    • git diff --cached --stat for already-staged changes
  3. Check recent commit style (optional)
    • git log --oneline -5
    • Match the existing commit message style
  4. Stage files
    • git add <path> [<path> ...] with explicit paths — never . or *
  5. Summarize what will be committed
    • git diff --cached --stat again, and list the files in a short bullet list
    • Explain the purpose of the changes
  6. Template drift check (requires template-sync-tools MCP)
    • If .claude/template-manifest.json exists in the repo root:
      1. Call template_compute_status(project_path=".")
      2. If any files have status PROJECT_CUSTOM or CONFLICT, append after the commit: "Template drift detected: X file(s) modified locally. Run /cct:contribute-upstream to push generalizable changes back, or /cct:sync-template to pull latest template updates."
      3. If any files have status AUTO_UPDATE, append after the commit: "Template updates available for X file(s). Run /cct:sync-template to apply."
    • If no manifest exists or template-sync-tools MCP is unavailable: skip silently
  7. Commit
    • git commit -m "<message>" — clear, concise, following repo conventions

Verification checklist

Before reporting the commit as done, confirm each of these:

  • git diff --cached --stat was shown to the user before committing
  • Only the intended files are staged — nothing swept in by a wildcard
  • git status --short after the commit shows a clean tree (or only deliberately-left files)
  • git log --oneline -1 shows the new commit with the intended message
  • No secrets, .env files, or local-only config are in the commit

Rules

  • MUST NOT commit without showing the user what will be committed
  • MUST NOT include files the user didn't intend to commit
  • If unsure which files to include, ASK the user
  • Template drift check is informational only — never block a commit
  • All manifest operations use MCP template-sync-tools — do NOT read/modify the manifest manually

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.

Reviews can't be read right now.

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