deliver

Prepares a reviewable GitHub pull request from a verified worker candidate without merging.

Updated Sep 5, 2026
One-click install
npx skills add https://github.com/douglasjarquin/sum --skill deliver-douglasjarquin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deliver
Source: https://github.com/douglasjarquin/sum/tree/main/grok-bots/sum/skills/deliver
Command: npx skills add https://github.com/douglasjarquin/sum --skill deliver-douglasjarquin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinators need a disciplined way to turn a worker's verified code candidate into a reviewable pull request without accidentally merging unfinished work or trusting the worker's own claims. ## Core Features & Use Cases - Verification Gating: Confirms the recorded verification run belongs to the coordinator and matches the candidate before any PR action. - Independent Review Enforcement: Defaults to a fresh independent review since a worker bot cannot review its own candidate. - Safe PR Management: Pushes the recorded branch without force, opens or adopts the existing GitHub PR, and avoids reopening closed PRs unless instructed. - Use Case: After a worker fixes a failing login test and verification passes, use this Skill to push the branch, open the PR, and hand the merge decision back to the user. ## Quick Start Use the deliver skill to open a pull request for the verified candidate in the current task and show me the PR URL without merging.

Frequently Asked Questions about deliver

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I open a pull request from a verified worker candidate?

Confirm the verification record matches the candidate, run an independent review, push the recorded branch without force, then open or adopt the existing GitHub PR for that branch. Show the user the full PR URL afterward.

Can this skill merge a pull request on GitHub?

No, merging is explicitly out of scope. The skill only prepares and opens the PR; the user always makes the merge decision, and merging requires separate explicit approval.

Why can't a worker bot review its own candidate code?

A worker bot cannot review its own candidate because self-review lacks independence. The skill defaults to a fresh independent review using separate review skills before opening or updating the PR.

What happens if the branch already has a closed pull request?

The skill will not open a new PR when the only pull requests for the branch are closed, unless the user explicitly says to. It adopts an existing open PR when one exists.

When should I not use the deliver skill?

Do not use it before coordinator verification is recorded, and never use it to merge, force-push, waive failing required checks, or delete unfinished work. Those actions require explicit user approval.