agentleFS
Sign inStart free
wtsi-hgiwtsi-hgi/agentskills/skills/deliver/SKILL.md

deliver

Skill1 starsChanged 40 days agoMITView on GitHub

Only when explicitly invoked, take the requested change and every resulting branch, including incidental fixes, through PR review and verified user merges.

25 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use prune, create-issue 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.
  • matthewpSkill

    prune

    Find and remove unused CSS in a Tideway project — classes defined in stylesheets but never referenced in markup. Use whenever the user wants to prune dead CSS, find unused styles or classes, clean up or slim a stylesheet, find orphaned BEM classes, or "tree-shake" hand-written CSS.

    Also in 3 projects that use this

  • sahinSkill

    create-issue

    Also in 3 projects that use this

  • BlockSkill

    plan

    Draft a TDD, PRD, or lightweight plan in the conversation without committing it.

    Also in 5 projects that use this

  • SentrySkill

    spec

    Produce a verified spec — problem, desired outcome, and acceptance criteria — before building. Use when given a GitHub/Linear issue link, when starting from a fuzzy in-conversation idea, or asked to "figure out what to do" / "scope this" / "what should I build" — whenever the *what* isn't yet pinned down. Grills the ambiguities, checks the premise against the code, and produces acceptance criteria you sign off on — then hands to design-first.

    Also in 4 projects that use this

  • AWSSkill

    ship

    Finalize dev work on an issue branch — update docs, push, and open a PR.

    Also in 5 projects that use this

  • AWSSkill

    wait-what

    Stop. That last message did not land: re-pitch it.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 25 edited versions we read keep these.

  • 8

    Distinctive

    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:

    Do this for every branch created during the work, including incidental fixes.

    line 9
  2. Distinctive:

    Use only when explicitly invoked.

    line 12
  3. Distinctive:

    Add incidental branches and update the record at every state change.

    line 21
  4. Distinctive:

    When a branch waits on a human merge, input, review, or CI, continue on an unblocked branch, respecting dependencies.

    line 24
  5. Distinctive:

    Create its PR, or update the existing one, with the change and validation.

    line 36
  6. Distinctive:

    Use pr-resolver on that PR through completion.

    line 37
  7. Distinctive:

    Ask for one merge at a time, choosing by dependency order, then user impact.

    line 40
  8. Distinctive:

    When the user reports a merge, verify on GitHub that the PR was merged into its intended target, then fetch the updated target.

    line 47

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

Deliver

Complete the requested change, then push, open a PR, and use pr-resolver. Do this for every branch created during the work, including incidental fixes. Track delivery until the user has merged them all.

Use only when explicitly invoked. This authorizes commits, feature-branch pushes, PR creation, and review resolution without asking again between steps. Honor narrower user instructions. Leave merging to the user.

Save the queue in the owner's branch-owned checklist or another project-approved location that survives cleanup. Record each branch, PR, target, dependencies, head SHA, status, what it waits on, and next action. Include its worktree per Workspace Boundary. Add incidental branches and update the record at every state change. On resume, reconcile it with live GitHub state before acting.

When a branch waits on a human merge, input, review, or CI, continue on an unblocked branch, respecting dependencies. Revisit waiting branches as results arrive. Pause the whole delivery only when no queued work can advance.

  1. Establish the branch worktree per Workspace Boundary. Complete the change using bugfix, orchestrator, or the project's applicable implementation and review skills. Preserve their tests, reviews, and completion requirements. Reuse completed work where its evidence still applies. Tell local workers to return before pushing or handling PR threads.
  2. Push the feature branch following agent-conduct. Create its PR, or update the existing one, with the change and validation.
  3. Use pr-resolver on that PR through completion. Confirm its current head meets the required checks and approvals and has no merge conflicts before calling it ready.
  4. Ask for one merge at a time, choosing by dependency order, then user impact. As soon as that PR is checked against the current target and ready, link it and ask the user to merge it and tell you when done. Give the planned order for the rest. Other PRs with that target stay queued until rebased onto each merged result and rechecked; do not present them as ready together. If PRs overlap in files, explain that they must merge in sequence. Continue other unblocked work while waiting; do not merge or enable auto-merge yourself.
  5. When the user reports a merge, verify on GitHub that the PR was merged into its intended target, then fetch the updated target. A closed PR or the user's report alone is not merge verification. Apply post-merge cleanup to its worktree, local branch, and stale remote-tracking refs, preserving the queue first. Report what was removed or kept and why. List any clones now eligible for deletion and ask once for permission to delete them.
  6. Rebase the next unblocked branch's remaining work onto its updated target, adjusting the PR base if a merged dependency requires it. Resolve conflicts, rerun the needed checks, and push following agent-conduct. Run pr-resolver again for a changed head; otherwise refresh its checks and review status. Preparing this next PR takes the next available worker slot ahead of long implementation, investigation, or soak work. If another worker can safely pause to free capacity, pause it and resume it afterwards. Repeat from step 4 when ready. Branches still needing implementation or a PR start at step 1, so every branch receives the full workflow.

Report blockers and respect the invoked skills' retry and wait limits. At each handoff, show the queue's status and exactly which PR the user should merge next, or what blocks it.

Delivery is complete only when every PR in the queue is verified merged and no branch remains unfinished. Return the merged PR links.

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