arn-shipping

Coordinate branching, committing, pushing, and PR creation in the Arness Code workflow.

31|3|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/AppsVortex/arness --skill arn-shipping
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arn-shipping
Source: https://github.com/AppsVortex/arness/tree/main/plugins/arn-code/skills/arn-shipping
Command: npx skills add https://github.com/AppsVortex/arness --skill arn-shipping

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates the end-to-end shipping workflow by coordinating prerequisite checks, invoking the ship operation, and guiding the user to the next stage in the pipeline.

Core Features & Use Cases

  • Ensures prerequisites are satisfied before shipping a feature.
  • Invokes the underlying ship skill to perform the actual commit, push, and PR logic without duplicating it.
  • Provides a clear handoff to the reviewing stage when shipping completes, enabling a smooth continuation of the Arness pipeline.

Quick Start

Initiate the arn-shipping flow to commit, push, and optionally create a PR.

Frequently Asked Questions about arn-shipping

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

FAQPage Schema
How do I automate git workflow orchestration for committing, pushing, and creating a pull request?

Automated git workflow orchestration coordinates branching, committing, pushing, and PR creation end-to-end. It performs prerequisite checks before invoking the ship operation, ensuring a smooth handoff to the reviewing pipeline stage.

What is the best way to ensure prerequisites are met before shipping a feature across projects?

Ensuring prerequisites before shipping a feature requires an orchestration workflow that validates requirements before invoking the ship operation. It commits changes and hands off to the reviewing stage without duplicating ship logic.

Can I automate pull request creation as part of a continuous delivery pipeline?

Automating pull request creation within a pipeline is supported by orchestration that commits and pushes code changes. It invokes the underlying ship logic to create the PR and guides the user to the next reviewing step.

Does this shipping workflow duplicate the underlying commit and push logic?

This shipping workflow does not duplicate commit and push logic. It orchestrates the pipeline by performing prerequisite checks, invoking the dedicated ship skill, and managing the handoff to the reviewing stage.

Why does my code shipping pipeline fail before reaching the pull request stage?

A code shipping pipeline fails before the PR stage if prerequisite checks are not satisfied. The orchestration workflow validates these requirements before it commits, pushes, and invokes the ship operation to create the pull request.