More screenshots
Works with the AI Agents you already use
Claude Code
Cursor
Codex CLI
Muse
Dots+22 moreClaude CodeCursorCodex CLIMuseDots
OpenClaw
Manus
Grok
Grok Bot+18 agents/ship: 5-Agent Feature Pipeline for Claude Code
Runs a feature through planner, coder, tester, reviewer and documenter subagents and ends with a reviewed local commit
Free
/ship: 5-Agent Feature Pipeline for Claude Code
Example session with this skill installed
/ship add an endpoint that shows a logged-in user how much of their daily and monthly transaction limits they have already used
- Read your context and instructions
- Compiled the ship
/ship run summary
Condensed from a real run on a Java/Spring backend. Service, class and file names are generalized.
Branch: feat/transaction-limit-usage in both services
Final verdict: SHIP (round 2)
Commits: one local commit per service on the feature branch. Nothing pushed or merged.
Stages
| Stage | Result |
|---|---|
| Planner | Spec with 4 open questions (which roles get access, what to show when an account isn't linked, how zero limits behave, what to return when the limits service is down). Run paused, I answered, run resumed. |
| Coder | Changes in 2 services, following each service's existing ports/adapters layout and router config style. Reused the existing Redis client and only added methods to it; no existing method was changed. |
| Tester | RESULT: PASS. 64 tests in service A, 158 in service B, including container tests on real PostgreSQL 14 and Redis 7. |
| Reviewer (round 1) | NEEDS WORK: 1 medium, 7 low findings, e.g. a predeploy permission check that missed wildcard routes, a non-JSON request answered with 500 instead of 415, a runtime error that should have returned 503. |
| Reviewer (round 2) | SHIP. All 8 resolved with file:line evidence; 2 low and 4 info items left as non-blocking notes. |
| Documenter | 5 doc files: OpenAPI path + schema + index entry, an API guide, a README section. Post-docs check: only documentation changed, nothing reverted. |
Example reviewer finding (round 1)
[MEDIUM] The predeploy SQL check only matched exact route strings. Real policies use Ant-style wildcards (
/**,/*/**), so an overlapping wildcard permission would pass the check. Convert patterns the same way the gateway does and add tests for the wildcard cases.
Non-blocking notes it left for me
- Two services read the shared internal key from differently named environment variables. Pick one name.
- Reset times use the JVM default zone in one service. Confirm the host timezone before deploy.
Next steps
- Review the diff on
feat/transaction-limit-usage. - Run the predeploy check on staging before applying the seed.
- Push and open a PR when you're happy. /ship never does this for you.
Connects securely to your tools. The creator never sees your data.
About this skill
What it does
/ship <feature request> takes one feature through five subagents, one after another. Each one does a single job and writes a small handoff file in .pipeline/ that the next one reads, so every stage starts with a clean, focused context.
| Stage | Model | Can edit | Writes |
|---|---|---|---|
| Planner | opus | only its spec | .pipeline/spec.md (files, signatures, edge cases, patterns to copy, open questions) |
| Coder | sonnet | code | code + .pipeline/changes.md (starts with the repo conventions it found) |
| Tester | sonnet | tests | tests + .pipeline/test-results.md (RESULT: PASS/FAIL) |
| Reviewer | opus | nothing (read-only) | .pipeline/review.md (VERDICT: SHIP / NEEDS WORK / BLOCK) |
| Documenter | sonnet | docs/ only | OpenAPI spec, a "how it works" doc, Mermaid diagrams |
Why I built it
When one agent plans, codes, tests and reviews a whole feature, it half forgets the plan, writes tests that agree with its own code, and then says everything looks fine. Splitting the work fixed most of that for me on real Java/Spring backend work.
Rules it follows
- Stops instead of guessing. Open questions in the spec, failing tests, or any verdict other than SHIP halt the run and come back to you.
- Follows your codebase. The coder studies 2-3 similar existing features first (layers, package layout, naming, DTO and error shapes) and writes them down. No new APIs, controllers, services or dependencies unless the spec needs them.
- Feature branch only. On main/dev/release it creates
feat/<slug>first. It never commits to, merges into or pushes a protected branch. Subagents can't run branch or commit commands at all. - Ends with a local commit. Nothing is pushed or merged. You review the diff.
- Docs come from the code. The documenter may only touch
docs/, README and CHANGELOG; anything else it changes is reverted.
What's in the zip
SKILL.md: the orchestratoragents/: planner, coder, tester, reviewer, documenter definitionsLICENSE: MIT
Install
- Unzip into
~/.claude/skills/(you get~/.claude/skills/ship/). - Recommended: copy
ship/agents/*.mdinto~/.claude/agents/. Installed subagents get their tool limits enforced by Claude Code (read-only reviewer, no-code planner). Without them the skill still runs each stage with a general-purpose subagent and checks the limits itself. - Restart Claude Code, open a git repo, and run
/ship <feature request>.
Limits
It's not magic: read the spec it writes and review the diff. It needs a git repository and a project whose tests can run locally.
Source and issues: https://github.com/Altafhossain72/claude-ship-pipeline
How to use
Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free forever
No account required to browse
Trust & safety
Security scanned
Verified clean today
- Free to download with an account
Requires
Git
Node.js