AGENT SKILL

ship

Review the dossier branch once, fold the fixup commits into the planned commits, hand the push and PR to the operator, then watch CI. Invoke when the user says "ds:ship", "ship the dossier", or when ds next exits 4.

License 许可
ISC
最近更新
2026-11-15
Stars
★ 3
Forks
0

01 前言 Front Matter

name
ship
description
Review the dossier branch once, fold the fixup commits into the planned commits, hand the push and PR to the operator, then watch CI. Invoke when the user says "ds:ship", "ship the dossier", or when ds next exits 4.

03 SKILL.md 正文

ds:ship

  1. ds check must print CHECK: OK.
  2. ds pack review writes the review pack. Spawn one reviewer agent with its path. It writes a findings file that ends VERDICT: PASS or VERDICT: CHANGES.
  3. ds record review <findings>. It stores the verdict with the tree hash.
    • On CHANGES: add one row per accepted finding with ds add, plan its commit, build it with /dossier:build, and come back to step 1. The next pack holds only the change since this review.
  4. The committer runs ds shape. It folds each fixup! commit into its planned commit. It refuses if the files would change.
  5. ds ship-args prints the repo, branch, base and PR title. Pass them to the ship tool. The push and the PR are the operator's card.
  6. After the push, run ds ci in the background. It waits for the CI runs of the pushed commit.
    • Exit 0 (CI: OK or CI: NONE): next is /dossier:close.
    • Exit 1: add one row per failed run with ds add, plan its commit, and build it with /dossier:build. The fix is a new planned commit.
    • Exit 2 or 3: tell the operator what it printed.

End each turn with the lines ds handoff prints.

Fixes after the first push become new planned commits. ds shape does not rewrite a pushed commit.

04 同仓库更多 Skills

raisedadead
raisedadead/claude-code-plugins

plan

Open a dossier and write its plan with the operator, then get it checked by a fresh agent before any build. Invoke when the user says "ds:plan", "start a dossier", "plan this", "grill me" in a repo with `.scratchpad/dossier/`, or when work needs more than one commit.

★ 3
raisedadead
raisedadead/claude-code-plugins

suite-review

Run the monthly evidence review of this repo's plugin skills. Count each skill's opportunities and uses with the census, read what happened where a skill was not used, put each skill in one bucket, act, and write the actions as predictions with a check date. Use when the operator says "suite review" or "monthly review", or when the suite-review line on LATER.md is due.

★ 3
raisedadead
raisedadead/claude-code-plugins

research-report

Research a technical question with probes on the local system, a web fan-out through deep-research, a grounding pass on every load-bearing claim, and a report rendered as one HTML page. Use when the user asks for a research report, a design study or an evidence-backed recommendation about their own system.

★ 3
raisedadead
raisedadead/claude-code-plugins

html-report

Render a markdown report as one self-contained HTML page for a human reader, in plain English, with the answer first, a table of contents and Mermaid diagrams drawn as images. Use when the user asks for an HTML report, or for a readable page made from a markdown document.

★ 3
raisedadead
raisedadead/claude-code-plugins

domain-modeling

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

★ 3
raisedadead
raisedadead/claude-code-plugins

codebase-design

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

★ 3