ship_with_review

Automate issue-to-merged-PR workflows with third-party code review loops.

1|Updated Oct 19, 2025
One-click install
npx skills add https://github.com/acartine/osterman --skill ship-with-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship_with_review
Source: https://github.com/acartine/osterman/tree/main/skills/ship_with_review
Command: npx skills add https://github.com/acartine/osterman --skill ship-with-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Traditional AI-assisted development suffers from operator thrashing—humans repeatedly review and request changes, causing slow, inefficient iterations. The ship_with_review skill automates an end-to-end workflow that takes an issue from intake to a merged PR by delegating third-party code review, enabling autonomous iteration until acceptance.

Core Features & Use Cases

  • End-to-end workflow from an issue (Beads or GitHub) to a merged PR with an automated third-party code review loop.
  • Iterative feedback handling with up to 5 review iterations and up to 3 CI fix attempts.
  • CI polling, squash merge, and automatic workspace cleanup after completion.

Quick Start

Ship the issue using the ship_with_review skill.

Frequently Asked Questions about ship_with_review

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

FAQPage Schema
How do I automate issue-to-merge pull request workflows with continuous code review?

Automated issue-to-merge workflows use a third-party code review loop to handle issue analysis, branch creation, PR generation, and CI polling until acceptance. This eliminates manual operator thrashing by delegating iterative feedback to an automated reviewer.

What is the best way to handle iterative code review cycles without manual intervention?

Iterative code review cycles can run autonomously by delegating feedback to a third-party automated reviewer, which handles up to 5 review iterations and 3 CI fix attempts before completing a squash merge and workspace cleanup.

Can I use automated PR workflows with GitHub or Beads issues for CI polling and merging?

Automated PR workflows apply directly to both Beads and GitHub issues, supporting worktree-based feature branches, CI polling, and squash merges. They require a SKILL.md frontmatter at the root directory to execute properly.

How does automated third-party code review handle CI failures and merge cleanup?

Automated third-party code review handles CI failures by iterating up to 3 fix attempts during continuous CI polling. After acceptance, it executes a squash merge and performs automatic workspace cleanup.

Why does my AI-assisted development workflow suffer from operator thrashing during PR reviews?

AI-assisted development workflows suffer from operator thrashing because humans repeatedly review and request changes, causing slow iterations. Automating the third-party code review loop enables autonomous iteration until acceptance, bypassing this bottleneck.

Do I need a SKILL.md frontmatter file to run automated issue-to-merge workflows?

A SKILL.md frontmatter with name and description at the root is required to run automated issue-to-merge workflows. Optional scripts, references, and assets directories can be included to support execution and documentation.