deliver-work

Delivers work candidates to requested endpoints such as commits, pull requests, and merges.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/pnewsam/skills --skill deliver-work-pnewsam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deliver-work
Source: https://github.com/pnewsam/skills/tree/main/registry/deliver-work
Command: npx skills add https://github.com/pnewsam/skills --skill deliver-work-pnewsam

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Finishing a change is more than writing code: teams still need to commit, push, open or update pull requests, respond to review threads, and merge safely without bypassing protections or losing evidence. This Skill brings a validated work candidate to exactly the endpoint the user requested, reusing existing validation and review evidence instead of redoing it. ## Core Features & Use Cases - Scoped delivery: Resolves the requested endpoint (local commit, pushed branch, draft PR, reviewed candidate, or merge) and stops there without expanding scope. - Runbook delegation: Routes concrete actions to runbooks such as publish-pr, rebase-pr, create-issue, and preserve-work, plus GitHub review and merge mechanics. - Verified completion: Reads back actual remote state, records commit/PR identity, and reports remaining CI or review conditions rather than claiming unverified success. - Use Case: After a reviewed change passes CI, ask the agent to update the PR title and body, reply to resolved review threads, and merge only when explicitly authorized, with the merge result verified afterward. ## Quick Start Use deliver-work to push my branch, open a pull request for the validated change, and report the PR link and any pending CI checks.

Frequently Asked Questions about deliver-work

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

FAQPage Schema
How do I deliver a code change to a pull request safely?▼

Identify the exact candidate, confirm current validation and review evidence, then use the publish-pr runbook to push and open or update the PR. Afterward, read back the remote state and record the PR identity and any pending CI or review conditions.

How to merge a GitHub pull request without bypassing protections?▼

Merge only when explicitly requested: refresh the PR head, required checks, review state, and mergeability, then use the repository's permitted merge method with an expected-head guard when available. Never use administrative bypass or change protections to force a merge.

Can I stop delivery at a commit or draft PR instead of merging?▼

Yes. Delivery resolves the requested endpoint from the user and work record, and may stop at local changes, a commit, a pushed branch, a draft PR, or a reviewed candidate. Successful implementation never expands the requested scope.

What happens if validation evidence is stale before publishing?▼

If evidence is missing or stale, the workflow continues through validate-work or review-work within the authorized task before publishing. It does not knowingly publish failures without an informed explicit override.

How should review threads be handled before merging?▼

Fetch all review threads with pagination, give each actionable thread a disposition such as fixed, deferred, or outdated, and resolve only threads whose resolution is verified against the current head. A request to dismiss one comment is not permission to dismiss an entire review.