From treeship
Use when the user finishes a meaningful unit of work (bug fix, feature, migration, refactor) and you need to close out the current Treeship session with a headline, summary, and review note that captures what actually happened.
How this skill is triggered — by the user, by Claude, or both
Slash command
/treeship:treeship-sessionThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Treeship records every tool call this session into a portable, signed receipt. The receipt is the user's, not ours -- it stays on their machine in `.treeship/sessions/` until they explicitly publish it.
Treeship records every tool call this session into a portable, signed receipt. The receipt is the user's, not ours -- it stays on their machine in .treeship/sessions/ until they explicitly publish it.
The Treeship Claude Code plugin starts a session automatically when work begins (via the SessionStart hook) and seals it automatically when the session ends (via SessionEnd). You normally don't need to touch the lifecycle commands.
You do need to close the session yourself, before SessionEnd fires, when:
Run, in order:
treeship session close \
--headline "<one sentence: what the agent accomplished>" \
--summary "<2-4 sentences: what changed and why>" \
--review "<what to verify, edge cases, anything risky>"
treeship session report
treeship session report prints a session report URL on treeship.dev. That URL is the human-readable page containing the cryptographic receipt -- it's what the user shares. Anyone who opens it can verify the embedded receipt themselves with treeship verify <url>, no account required.
The headline shows up in the report's title and in any future search. Treat it like a commit message:
The summary is for someone reading the report a week later. Cover what changed, why, and any non-obvious decisions.
The review note tells whoever opens the report what to look at first. Risks, edge cases, things you weren't sure about, things you decided to defer -- this is where they go.
treeship session close seals the receipt locally. Nothing leaves the machine.treeship session report is the only command that uploads. It produces the shareable URL.auto_push: true in .treeship/config.yaml, in which case session close itself publishes. Don't assume either way -- run report explicitly when the user wants a URL.Provides a checklist for code reviews covering functionality, security, performance, maintainability, tests, and quality. Use for pull requests, audits, team standards, and developer training.
npx claudepluginhub zerkerlabs/treeship --plugin treeship