agentleFS
Sign inStart free
JeroenGarJeroenGar/skills/checkpoint-commit/SKILL.md

checkpoint-commit

Skill2 starsChanged 2 months agoMITView on GitHub

Commit and push the current task's relevant changes without hooks or checks, then open a draft GitHub PR if the branch has no open PR. Use only when the user explicitly asks for a checkpoint commit.

  • Commits and pushes

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. dhslegen/digital-delivery-team★ 1same name

    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.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    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:

    Treat the request as approval to publish the current reviewed slice.

    line 8
  2. Distinctive:

    Read the task context, git status --short --branch, and the current branch.

    line 12
  3. Distinctive:

    Create a new commit with a short message describing the slice.

    line 15
  4. Very specific:

    Check for an open PR whose head is the current branch.

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Checkpoint commit

Treat the request as approval to publish the current reviewed slice. Scope it, commit it, push it, ensure it has a PR, and return.

Workflow

  1. Read the task context, git status --short --branch, and the current branch. Identify only the files changed for the current task. Inspect file names or a concise diff only when needed to resolve scope. Do not review the implementation again.
  2. Preserve unrelated changes. Stage relevant paths explicitly with git add -- <paths>, including relevant untracked files. Do not use git add . or git add -A when the worktree contains unrelated changes.
  3. Confirm the staged file list matches the task. If nothing relevant changed, return without creating an empty commit.
  4. Create a new commit with a short message describing the slice. Use git commit --no-verify; do not amend an earlier commit.
  5. Push the current branch with git push --no-verify. If it has no upstream, use git push --no-verify -u origin HEAD. Never force-push.
  6. Check for an open PR whose head is the current branch. Reuse any existing open PR without changing its draft state. If none exists, create one with gh pr create --draft --fill.
  7. Return immediately with:
    • A one-line summary containing the short commit SHA and branch.
    • A compact tree of the files in the new commit. Derive the paths from the commit, not the remaining worktree.
    • A clickable Markdown link to the PR, including its number and title when available.

Do not run tests, formatters, linters, builds, hooks, CI commands, or GitHub checks. Do not wait for or monitor CI. If the branch is detached, the current branch is the repository's default branch, the relevant file set is ambiguous, or commit, push, or PR creation fails, stop and report the blocker without expanding into unrelated cleanup or diagnosis.

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