skills.rest
jp5labs
jp5labsOFFICIAL
Explore all skills by this author →
GitHub

forge-deliver

Orchestrates GitHub issue delivery workflows from commit through pull request and issue comment.

1|Updated Apr 8, 2026
Search Tags:#git automation#pull request#github#cli#issue tracking#code delivery#delivery workflow
One-click install
npx skills add https://github.com/jp5labs/forge-workflow --skill forge-deliver-jp5labs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: forge-deliver
Source: https://github.com/jp5labs/forge-workflow/tree/main/forge_workflow/templates/skills/forge-deliver
Command: npx skills add https://github.com/jp5labs/forge-workflow --skill forge-deliver-jp5labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping finished work to GitHub involves repetitive ceremony: committing, pushing, opening a PR, commenting on the issue, and cleaning up after merge. This Skill standardizes that entire delivery lifecycle so every change follows the same disciplined, auditable path. ## Core Features & Use Cases - Four delivery modes: Choose full, standard, quick, or ship mode to match the ceremony level to the risk of the change, from architecture-touching work down to single-file fixes. - Sub-skill orchestration: Invokes assessment, planning, branch setup, and post-merge cleanup skills as part of the full lifecycle. - Review gates and mode awareness: Respects a needs-human-gate issue label and a CLAUDE_MODE environment variable to decide whether human review is required before delivery. - Use Case: After implementing a fix for issue #153, run the standard mode to plan, branch, implement, and deliver a PR with an auto-generated issue comment in one guided flow. ## Quick Start Ask the assistant to deliver issue 153 in standard mode using the forge-deliver workflow.

Frequently Asked Questions about forge-deliver

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

FAQPage Schema
How do I deliver a GitHub issue as a pull request?▼

Run the delivery workflow with a mode and issue number, such as standard mode for issue 153. It creates the branch, commits staged changes, pushes, opens the PR, and posts an issue comment automatically.

What is the difference between full, standard, quick, and ship delivery modes?▼

Full adds pre-implementation assessment and planning gates, standard skips the assessment, quick handles low-risk single-file changes without a formal plan, and ship only commits, pushes, and opens a PR for work already on a branch.

Can I deliver only some of my modified files?▼

Yes. The delivery CLI commits only what is already staged, so run git add on the specific files first, then invoke the delivery run command. Do not manually commit and use skip-commit as a workaround.

Does the delivery workflow require human review before creating a PR?▼

It depends on configuration. If the issue has a needs-human-gate label or CLAUDE_MODE is supervised or unset, the workflow waits for a human review signal. In autonomous mode it proceeds directly to delivery.

How do I test the delivery flow without making changes?▼

Add the dry-run flag to the delivery run command. It validates the entire commit, push, PR, and comment flow without performing any mutations on the repository or GitHub.

Related Skills

Explore More Software Engineering Skills→
dokipendokipen
1

refine

Refine GitHub Issues with acceptance criteria, estimates, and labels.

Community
Advanced
devbasexdevbasex
1

merged

Delete merged branches and worktrees with approval, then update the base branch.

Official
Advanced
Open-PawsOpen-Paws
3

code-review

Automate layered code review for pull requests in CI pipelines.

Official
Advanced
PracticalSwanPracticalSwan
7

devops-tooling

Guide Git workflows, Bash and PowerShell scripting, and CI/CD pipelines.

Community
Intermediate