skills.rest
heliohq
heliohqOFFICIAL
Explore all skills by this author →
WebsiteGitHub

handoff

Coordinates GitHub pull requests from commit to ready-for-merge state.

88|6|Updated Mar 25, 2026
Search Tags:#pull request#handoff#code delivery#merge readiness#ci recovery#github checks
One-click install
npx skills add https://github.com/heliohq/ship --skill handoff-heliohq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/heliohq/ship/tree/main/skills/handoff
Command: npx skills add https://github.com/heliohq/ship --skill handoff-heliohq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of delivering finished work by handling the full handoff loop from local verification to a merge-ready pull request.

Core Features & Use Cases

  • Release Coordination: Commit the related changes, push the branch, create or update the PR, and keep the delivery moving.
  • CI and Review Recovery: Watch GitHub checks, read failures and review feedback, then fix and repush until the PR is green.
  • Merge Readiness Control: Sync with base, resolve conflicts, and ensure the branch is actually ready to merge rather than merely opened.
  • Use Case: A feature branch is done, but tests, review comments, and branch protection still need attention before shipping.

Quick Start

Use the handoff skill to verify the current branch, ship the related changes, and keep iterating until the pull request is merge-ready.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I make a pull request merge-ready after my feature branch is done?▼

Creating a merge-ready pull request involves committing and pushing finished code changes, running local checks, monitoring GitHub CI checks, and iterating on fixes until the branch passes verification and meets merge readiness criteria.

What is the best way to handle CI recovery when GitHub checks fail on a pull request?▼

Handling CI recovery for failed GitHub checks means reading failure logs, applying fixes, and repushing the branch. The handoff loop iterates through this fix and repush cycle until CI checks pass or the issue is escalated.

Does the handoff process automatically resolve merge conflicts before shipping code changes?▼

Yes, the handoff process inspects merge state and syncs with the base branch to resolve conflicts, ensuring the branch is actually ready to merge rather than merely opened, before shipping the completed code changes.

Can I use this process for delivering documentation updates and refactors, not just features?▼

Yes, you can use this handoff process for delivering documentation updates and refactors. It applies to any finished code changes including bug fixes that require local verification, commit, push, and pull request delivery.

What happens if my branch still fails checks after multiple fix and repush loops?▼

If a branch still fails checks after multiple fix and repush loops during CI recovery, the handoff process escalates the issue rather than continuing to iterate, preventing an endless loop of failed GitHub checks.

Related Skills

Explore More Software Engineering Skills→
lapaixkemsdortshlee-svglapaixkemsdortshlee-svg

verification-before-completion

Require fresh verification command output before declaring work complete.

Community
Basic
electroheadfxelectroheadfx
4

gsd-ship

Push a verified branch and create a merge-ready pull request.

Community
Advanced
mvillmowmvillmow
18

verify-pr-ready

Verify GitHub pull requests for CI checks, approvals, and merge conflicts.

Community
Basic
sergicalsergical
1

iterate-pr

Automate fixing pull request failures and review feedback until CI checks pass.

Community
Advanced