forge-ship
/forge-ship
Implementuje zgłoszenie lub plan i od razu robi recenzję w świeżym kontekście, a z opcją --guard czeka na CI i recenzentów do werdyktu ryzyka.
- Autor
- mgratzer ↗
- Repozytorium
- forge ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 25.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 2
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 25.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Implementuje zgłoszenie lub plan i od razu robi recenzję w świeżym kontekście, a z opcją --guard czeka na CI i recenzentów do werdyktu ryzyka.
Oryginalny opis (EN)
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. With --guard it also waits for CI and peer review, addresses feedback until the PR is review-ready, and ends with a risk verdict (merge-ready or review-ready, or merged when the project opts in). Use when the user wants to implement and review without manual handoff between skills.
Jak działa
- Input
- Process
- Output Format
- Guidelines
- Related Skills
- Example Usage
Podgląd SKILL.md
--- name: forge-ship description: 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. With --guard it also waits for CI and peer review, addresses feedback until the PR is review-ready, and ends with a risk verdict (merge-ready or review-ready, or merged when the project opts in). Use when the user wants to implement and review without manual handoff between skills. disable-model-invocation: true --- # 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. **Guard mode:** `--guard` continues after the PR is open with the [forge-guard](../forge-guard/SKILL.md) process — quality passes, CI, peer review, feedback rounds — then the [forge-land](../forge-land/SKILL.md) risk verdict, and ends at `merged` (only with the project's auto-merge opt-in), `merge-ready`, `review-ready`, or `needs-human`. Implies `--unattended`. ## Process ### Step 1: Implement Execute 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 and pushed; deferred items become Issues — see [issue-operations](_shared/issue-operations.md). ### Step 4: Guard and Land (only with `--guard`) Run the full [forge-guard](../forge-guard/SKILL.md) process on the PR from Step 1. When it ends at `needs-human`, that is this skill's terminal state. When it reaches `review-ready`, don't report that state: run the full [forge-land](../forge-land/SKILL.md) process on the same PR, and its terminal state is this skill's. Without `--guard`, report `pushed` via [status-reporting](_shared/status-reporting.md) — the PR is open and self-reviewed, and the human takes it from there. ### Step 5: Summarize Report implementation, review, guard, and land results together. ## Output Format ```text ## Ship Summary **PR:** #<number>: <title> **Branch:** <branch-name> **Result:** pushed | merged | merge-ready | review-ready | needs-human (<reason>) ### Implementation - <N> commits, <M> files changed - Tests: <added/modified/none> - Docs: <updated/none> - Exercised: <intended | wrong: <observed vs expected> | not exercised: <why>> (plus "not run: <parts>" when parts were skipped) ### Review Findings - Fixed in PR: <list or "none"> - Deferred: #<issue> (<title>), or "none" ### Guard (guard mode only — the Passes, Rounds, and Open sections from forge-guard; Result above is authoritative) ### Land (guard mode only, when guard reached review-ready — Judged, Checks, and Review requested from forge-land) ### 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`, the fresh-context review flow shared with `forge-reflect` (`_shared/review-delegation.md`), and `forge-guard` followed by `forge-land` when `--guard` is set. **After peer review:** Use `forge-address-pr-feedback` to address reviewer comments (guard mode does this for you). **Many Issues at once:** Use `forge-batch` to group Issues into Waves, then start one `forge-ship --guard` session per Issue. ## Example Usage ``` /forge-ship 42 /forge-ship 42 -- keep the diff minimal /forge-ship docs/roadmap.md /forge-ship --unattended 42 /forge-ship --guard 42 ```
Pliki w paczce (2)
- SKILL.md 5 KB
- _shared 1 KB
Wersje
W bazie nie ma innych skilli o nazwie forge-ship.
Migawka bazy z 13.11.2026 · wersja paczki ae17ba188283 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 95forge-land
Ocenia, czy zielony pull request wymaga decyzji człowieka, sprawdza scalanie i ryzyko, a potem zapisuje wynik w opisie PR. - 100implement-issue
Realizuje zgłoszenie z GitHub od początku do końca: tworzy gałąź, publikuje plan do zatwierdzenia, implementuje i obsługuje recenzję PR. - 100forge-implement
Implementuje funkcję lub poprawkę ze zgłoszenia, pliku planu albo opisu, zgodnie ze standardami projektu, i kończy na otwarciu pull requesta. - 100dev-issue
Wdraża zgłoszenie z GitHuba od początku do końca i przygotowuje pull request gotowy do scalenia. - 86review
Przegląda pull request albo gałąź względem celu i kończy werdyktem, czy można scalić, z listą uwag. - 100full
Przeprowadza zgłoszenie Linear od początku do końca: uruchamia /start, potem /finish, zależnie od werdyktu /quality-review, z tokenami wt, auto, simple, pr i push.