skills.rest
FerroxLabs
FerroxLabsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

ferrox-ship

Push the current branch, open a pull request, and track the merge outcome.

21|9|Updated Jul 21, 2026
Search Tags:#pull request#github#verification#shipping#merge tracking#branch push
One-click install
npx skills add https://github.com/FerroxLabs/ferrox-factory --skill ferrox-ship
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ferrox-ship
Source: https://github.com/FerroxLabs/ferrox-factory/tree/main/skills/ferrox-ship
Command: npx skills add https://github.com/FerroxLabs/ferrox-factory --skill ferrox-ship

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of turning a completed local change into a merged pull request, so verified work can leave your machine cleanly and predictably.

Core Features & Use Cases

  • Branch Push and PR Creation: Pushes the current branch and opens a pull request with an auto-generated body.
  • Verification-Aware Shipping: Assumes the work has passed verification and uses that state to drive the ship workflow.
  • Merge Tracking: Can optionally trigger review and follow the work through to merge.
  • Use Case: After a phase or milestone is finished and /ferrox-verify-work succeeds, use this Skill to publish the change as a PR and continue toward merge.

Quick Start

Ask the assistant to ship the verified branch for phase 4 and open the pull request.

Frequently Asked Questions about ferrox-ship

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

FAQPage Schema
How do I ship a verified local branch and open a pull request?▼

Merge tracking is the process of optionally triggering a review and following your pull request through to the final merge outcome. This ensures your shipped work is fully integrated into the target branch.

When should I use an automated pull request workflow for shipping code?▼

You should use an automated pull request workflow for shipping code after a feature phase, milestone, or build increment is finished and has passed local verification, ensuring only validated changes leave your machine.

Does the branch push and PR creation process require prior verification?▼

Yes, the branch push and PR creation process is verification-aware and assumes your local work has passed verification. It uses this verified state to drive the end-to-end delivery workflow for clean and predictable shipping.

Can I trigger a code review after opening a pull request?▼

Yes, you can optionally trigger a code review after opening a pull request. The Skill tracks the merge outcome by following the work through the review process toward final integration on the target branch.

Related Skills

Explore More Software Engineering Skills→
NUMU-IONUMU-IO
2

speckit-ship-run

Automates release shipping workflows and pull request preparation for spec-driven feature branches.

Official
Advanced
drillandrillan
1

merge-pr

Wait for CI checks and merge GitHub pull requests with a chosen strategy.

Community
Advanced
khapn-2933khapn-2933

tkm:git

Automate git staging, committing, pushing, and pull requests with conventional commits.

Community
Advanced
paultyngpaultyng
9

push-and-watch

Push local commits, create draft pull requests, and monitor GitHub Actions CI runs.

Community
Intermediate