How do I install the Forge Ship skill?

Run npx skillmds@latest add mgratzer/forge-ship in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Forge Ship safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Forge Ship?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Forge Ship free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Forge Ship?

mgratzer (@mgratzer) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Forge Ship by mgratzer — Agent Skill

Name: Forge Ship
Author: mgratzer

Forge Ship

End-to-end implementation and self-review in a single invocation — implements from an Issue, plan file, or free-text description, then runs a lean fresh-context review. Use when the user wants to implement and review without manual handoff between skills.

mgratzer 7aafc5a 3.2 KB Updated Sep 17, 2026

File contents

Ship a Change

Implement end to end — code it, review it, ship it. Implementation runs in the current session; review always delegates to fresh context and deepens only when risk justifies it.

Input

Same as forge-implement ($ARGUMENTS): Issue number/URL, plan file path, or free-text. Optional: -- <additional context>.

Unattended mode: --unattended skips plan approval and auto-triages findings by severity.

Process

Step 1: Implement

Execute the full forge-implement process with one modification: do not produce implement's summary — the review below informs the single final report.

Step 2: Review (delegate)

Follow the review-delegation process: collect the diff from the implementation, use one fresh-context review pass by default (this session authored the diff, so the inline tiny-diff path never applies), add a second pass only when risk justifies it, and aggregate findings.

Inputs provided to sub-agent: the branch diff, changed file list, and project conventions per review-delegation. Expected output: Deduplicated findings grouped by file with severity tags (P0/P1/P2).

Step 3: Triage Findings

In attended mode (default): present each finding to the user with a recommendation, biased hard toward fix now — defer only changes that materially expand PR scope or are truly out of scope.

In unattended mode: auto-triage by severity plus scope from the review rubric: fix P0–P2 in-scope findings now; defer P1–P2 items that are truly out of scope or materially larger; ignore P3.

Fixed findings are committed; deferred items become Issues — see issue-operations.

Step 4: Summarize

Report implementation and review results together.

Output Format

## Ship Summary

**PR:** #<number> — <title>
**Branch:** <branch-name>

### Implementation
- <N> commits, <M> files changed
- Tests: <added/modified/none>
- Docs: <updated/none>

### Review Findings
- Fixed in PR: <list or "none">
- Deferred: #<issue> — <title> (or "none")

### Quality Gates
- Lint: ✓/✗
- Format: ✓/✗
- Types: ✓/✗
- Tests: ✓/✗
- Coverage: ✓/✗/not configured

Guidelines

Even tiny diffs delegate here — this session authored the changes, so inline review would be self-review
Don't skip the review — even if implementation felt clean
Bias toward fixing in the same PR — unless a finding is truly larger or out of scope

Related Skills

Components: Composes forge-implement and the fresh-context review flow shared with forge-reflect (_shared/review-delegation.md). After peer review: Use forge-address-pr-feedback to address reviewer comments.

Example Usage

/forge-ship 42
/forge-ship 42 -- keep the diff minimal
/forge-ship docs/roadmap.md
/forge-ship --unattended 42

---name: forge-shipdescription: End-to-end implementation and self-review in a single invocation — implements from an Issue, plan file, or free-text description, then runs a lean fresh-context review. Use when the user wants to implement and review without manual handoff between skills.---# Ship a ChangeImplement end to end — code it, review it, ship it. Implementation runs in the current session; review always delegates to fresh context and deepens only when risk justifies it.## InputSame as `forge-implement` (`$ARGUMENTS`): Issue number/URL, plan file path, or free-text. Optional: `-- <additional context>`.**Unattended mode:** `--unattended` skips plan approval and auto-triages findings by severity.## Process### Step 1: ImplementExecute the full [forge-implement](../forge-implement/SKILL.md) process with one modification: **do not produce implement's summary** — the review below informs the single final report.### Step 2: Review (delegate)Follow the [review-delegation](../_shared/review-delegation.md) process: collect the diff from the implementation, use one fresh-context review pass by default (this session authored the diff, so the inline tiny-diff path never applies), add a second pass only when risk justifies it, and aggregate findings.**Inputs provided to sub-agent:** the branch diff, changed file list, and project conventions per review-delegation.**Expected output:** Deduplicated findings grouped by file with severity tags (P0/P1/P2).### Step 3: Triage Findings**In attended mode (default):** present each finding to the user with a recommendation, biased hard toward **fix now** — defer only changes that materially expand PR scope or are truly out of scope.**In unattended mode:** auto-triage by severity plus scope from the [review rubric](../_shared/review-rubric.md): fix P0–P2 in-scope findings now; defer P1–P2 items that are truly out of scope or materially larger; ignore P3.Fixed findings are committed; deferred items become Issues — see [issue-operations](../_shared/issue-operations.md).### Step 4: SummarizeReport implementation and review results together.## Output Format```text## Ship Summary**PR:** #<number> — <title>**Branch:** <branch-name>### Implementation- <N> commits, <M> files changed- Tests: <added/modified/none>- Docs: <updated/none>### Review Findings- Fixed in PR: <list or "none">- Deferred: #<issue> — <title> (or "none")### Quality Gates- Lint: ✓/✗- Format: ✓/✗- Types: ✓/✗- Tests: ✓/✗- Coverage: ✓/✗/not configured```## Guidelines- **Even tiny diffs delegate here** — this session authored the changes, so inline review would be self-review- **Don't skip the review** — even if implementation felt clean- **Bias toward fixing in the same PR** — unless a finding is truly larger or out of scope## Related Skills**Components:** Composes `forge-implement` and the fresh-context review flow shared with `forge-reflect` (`_shared/review-delegation.md`).**After peer review:** Use `forge-address-pr-feedback` to address reviewer comments.## Example Usage```/forge-ship 42/forge-ship 42 -- keep the diff minimal/forge-ship docs/roadmap.md/forge-ship --unattended 42```

Frequently asked questions