agentleFS
SuShuhengSuShuheng/making-things/skills/github-delivery/SKILL.md

github-delivery

Skill1 starsChanged 4 months agoMITView on GitHub

Use when a verified work item explicitly requires Git branch creation, intentional commits, non-force push, pull-request handoff, or authorized artifact delivery. Do not use outside a Git repository or to publish a formal Release without explicit authorization.

  • Commits and pushes

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run fresh required verification and inspect the final diff before staging.

    line 14
  2. Distinctive:

    Create or update a PR only when requested.

    line 17
  3. Distinctive:

    Do not change remotes or credentials to make push succeed.

    line 23

≈ “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

GitHub Delivery

Deliver only the verified, authorized scope.

  1. Require explicit user authorization for the requested Git action. Read the sidecar task/track evidence, repository instructions, and references/git-delivery-policy.md.
  2. Confirm Git repository, current branch, clean understanding of unrelated changes, remote, authentication, and requested destination.
  3. Run fresh required verification and inspect the final diff before staging.
  4. Stage only intended paths; create a descriptive commit without rewriting unrelated history.
  5. Push the branch without force only when a remote exists and authentication succeeds.
  6. Create or update a PR only when requested; include task evidence, risks, platform gaps, and release impact.
  7. Record commit SHA, branch, remote, push/PR result, and any artifact destination in the selected sidecar task Result. This Skill never creates a worktree or chooses a task automatically.

Do not change remotes or credentials to make push succeed. Git push, artifact upload, draft Release, formal Release, and registry publication are separate authorizations.

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.