AutoGineer
Generated banner for Factory Ship
Generated logo for Factory Ship

Factory Ship

Builder.ioOfficialPublished by Builder.io

  • Skill
  • Workflow
  • Software development
  • MIT
  • No issues found
Download ZIP

From the author

Experimental workflow for publishing and completing configured software delivery work. Use when the user or an enabled factory policy asks to ship.
— the description by Builder.io

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

Factory Ship provides a structured, multi-step procedure for publishing and completing software delivery tasks. It emphasizes verification, authorization, and adherence to repository-specific configurations. The workflow guides the agent through confirming ownership, running quality checks, managing pull requests, resolving feedback, and handling merge gates, ensuring that delivery actions are only performed when explicitly enabled and verified.

What it does

  • Confirms task ownership and identifies the correct worktree and branch.
  • Executes configured formatters, tests, and release checks.
  • Manages pull request creation and updates based on authorization.
  • Processes feedback and performs coherent code updates.
  • Enforces merge gates and verifies state against live head conditions.
  • Handles post-merge cleanup, issue closure, and notification tasks.

When to use it

  • When a user or factory policy requests to ship software delivery work.
  • When you need to automate the publication of code changes to a repository.
  • When you need to ensure all quality checks are passed before merging.
  • When you need to resolve feedback on an existing pull request.

Advantages

  • Ensures consistent delivery procedures across different projects.
  • Reduces errors by enforcing strict verification and authorization steps.
  • Maintains clean worktree management by avoiding peer checkout interference.
  • Provides clear stop conditions to prevent unauthorized or incomplete actions.

Usage examples

“Ship the current changes to the repository.”
The agent will identify the target branch, run the configured tests, and open a pull request if authorized by the factory policy.
“Resolve the feedback on my PR and merge it.”
The agent will compare the comments with the current code, apply the necessary updates, rerun checks, and proceed with the merge if all gates are satisfied.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/builderio/factory-ship/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip factory-ship.zip -d .agents/skills

Documentation by Builder.io

Factory Ship

Start with the Factory guide for workflow setup and configuration.

Read .agent-factory/config.yaml, the optional skill_prompts.factory-ship entry, and the repository's instructions before publishing. See the Factory configuration reference. The prompt adds project guidance; editing code does not by itself authorize a PR update, approval, merge, or deployment.

Delivery steps

  1. Confirm ownership. Identify the target repository, task-owned worktree, branch, and complete task-related change set. Preserve unrelated changes. Use a clean automation-owned worktree when the scheduler provides one; never take over a peer's checkout.

  2. Verify changes. Run the configured formatter, tests, and release checks. Report checks that were skipped or unavailable.

  3. Publish when enabled. Open or update a PR only when authorized. Apply configured title, body, draft status, labels, and communication rules. Do not tag or message people unless enabled.

  4. Resolve feedback. Compare comments with the code and current human direction. Make one coherent update, then rerun affected checks.

  5. Apply merge gates. Merge only under its own enabled policy and while all criteria hold on the unchanged live head. Use a head-match guard when the host supports it. A head change invalidates tied evidence and resets the soak.

  6. Verify and close out. Confirm the merge in the current base branch. Verify deployment only when configured; a merge is not live proof. Close issues, rotate worktrees, and notify only at their configured proof points.

Stop conditions

Hold the work when ownership, authorization, a required check, or live host state is missing or unclear. State the exact next step; do not turn an inconclusive result into success.

Files

SKILL.md

Factory Ship

Start with the Factory guide for workflow setup and configuration.

Read .agent-factory/config.yaml, the optional skill_prompts.factory-ship entry, and the repository's instructions before publishing. See the Factory configuration reference. The prompt adds project guidance; editing code does not by itself authorize a PR update, approval, merge, or deployment.

Delivery steps

  1. Confirm ownership. Identify the target repository, task-owned worktree, branch, and complete task-related change set. Preserve unrelated changes. Use a clean automation-owned worktree when the scheduler provides one; never take over a peer's checkout.

  2. Verify changes. Run the configured formatter, tests, and release checks. Report checks that were skipped or unavailable.

  3. Publish when enabled. Open or update a PR only when authorized. Apply configured title, body, draft status, labels, and communication rules. Do not tag or message people unless enabled.

  4. Resolve feedback. Compare comments with the code and current human direction. Make one coherent update, then rerun affected checks.

  5. Apply merge gates. Merge only under its own enabled policy and while all criteria hold on the unchanged live head. Use a head-match guard when the host supports it. A head change invalidates tied evidence and resets the soak.

  6. Verify and close out. Confirm the merge in the current base branch. Verify deployment only when configured; a merge is not live proof. Close issues, rotate worktrees, and notify only at their configured proof points.

Stop conditions

Hold the work when ownership, authorization, a required check, or live host state is missing or unclear. State the exact next step; do not turn an inconclusive result into success.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
Builder.io
Publisher
Builder.io (Official)
Source
BuilderIO/skills · skills/factory-ship · commit f4f10b8
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Builder.io or Builder.io.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download factory-ship.zip