explaingit

hamen/ship-feature

Analysis updated 2026-05-18

3ShellAudience · developerComplexity · 3/5LicenseSetup · moderate

TLDR

A shared workflow and CLI that makes AI coding agents plan, get reviewed, and get merged through the same gated process, with a human approving the plan and the merge.

Mindmap

mindmap
  root((ship-feature))
    What it does
      Defines a shared workflow
      Gates plan and merge
      Wraps pr-review-relay
    Tech stack
      Shell CLI
      WORKFLOW.md
      pr-review-relay
    Use cases
      Standardized agent workflow
      Human approval gates
      Multi-agent plan review
    Audience
      Developers using AI agents

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Standardize how AI coding agents plan and ship changes across a team

USE CASE 2

Require human approval before an agent's plan is implemented

USE CASE 3

Fan an implementation plan out to multiple agents for review at once

USE CASE 4

Scan a repo for personal data before making it public

What is it built with?

ShellBashpr-review-relay

How does it compare?

hamen/ship-featurebechsteindigital/claude-shiploophannes/quack
Stars333
LanguageShellShellShell
Last pushed2024-06-05
MaintenanceDormant
Setup difficultymoderatemoderatemoderate
Complexity3/54/54/5
Audiencedevelopervibe coderdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 30min

Requires pr-review-relay already installed on your PATH for the cross-review step to work.

In plain English

ship-feature is a workflow and small command line tool for teams that use AI coding agents like Claude, Codex, or Cursor to make changes to a codebase. Instead of each agent inventing its own process for planning, reviewing, and merging changes, ship-feature writes that process down once, in a single file called WORKFLOW.md, and gives each agent a thin adapter that points to it. The workflow itself has seven steps: plan the change, have a second agent review that plan, get your approval as a human, implement the change in a separate worktree and open a pull request, run cross review and tests while any real problems remain, merge the change yourself, and finally verify the result on the merged commit. Only two of those steps require you personally to step in and approve something: approving the plan before any code is written, and approving the actual merge. The agent is never allowed to merge its own work under this process. The cross review step is handled by a separate related project called pr-review-relay, which this tool requires to already be installed and available on your system path. ship-feature's own command line tool adds a preflight check that confirms you are working in a proper feature branch before you start, a way to send an implementation plan out to several agents at once for a read only review, and a transparent wrapper around pr-review-relay that preserves its normal output and exit codes while explaining what each one means to you. Installation is done by cloning the repository and running an install script, which links the command line tool, copies the workflow file and a matching skill definition into your agent configuration folders, and adds a marked section to your Codex configuration if you use it. The project includes two separate privacy scanning scripts: one that runs automatically in continuous integration to catch accidentally committed emails or file paths, and one meant to be run locally before publishing that checks your full history against a private list of things to scrub first.

Copy-paste prompts

Prompt 1
Help me install ship-feature and set up its WORKFLOW.md in my project.
Prompt 2
Explain the two human approval gates in ship-feature's workflow.
Prompt 3
Walk me through using ship-feature plan-review to get my plan reviewed by multiple agents.
Prompt 4
Show me how ship-feature's privacy scanning scripts work before I publish a repo.

Frequently asked questions

What is ship-feature?

A shared workflow and CLI that makes AI coding agents plan, get reviewed, and get merged through the same gated process, with a human approving the plan and the merge.

What language is ship-feature written in?

Mainly Shell. The stack also includes Shell, Bash, pr-review-relay.

How hard is ship-feature to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is ship-feature for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.