Skip to content
Skills Library
Programming · Writing

treeship-session

/treeship-session

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.

Repository
treeship ↗
Licence
Apache-2.0
Last repository change
27.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

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.

Original author description

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 it works

  1. Closing the session
  2. Writing good headlines and summaries
  3. What stays local vs. what gets published
  4. When NOT to close
Original SKILL.md headings · 50 lines, 444 words
SKILL.md preview
---
name: treeship-session
description: 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.
allowed-tools: Bash
---

# Treeship session lifecycle

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:

- The user finishes a meaningful unit of work and you want the receipt to carry a real headline (not the generic auto-headline).
- The user explicitly asks for "the receipt" / "the proof" / "a session report" / "the verification URL".
- The user is about to share what just happened with a teammate, customer, or reviewer.

## Closing the session

Run, in order:

```bash
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.

## Writing good headlines and summaries

The headline shows up in the report's title and in any future search. Treat it like a commit message:

- **Specific, not generic**: "Switch session storage from sqlite to LMDB to fix lock contention" beats "fix database stuff".
- **Past tense**: describes what was done, not what was planned.
- **One sentence**: under ~80 characters if possible.

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.

## What stays local vs. what gets published

- `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. Always run it explicitly when the user wants a URL -- there is no automatic push on session close (`auto_push: true` is accepted in config but not implemented).

## When NOT to close

- Sub-tasks of the same conversation. Use one session per user-meaningful unit of work, not per agent step.
- The user has not actually finished. Wait for the explicit "ok we're done" / "now let's wrap up" signal.

Versions

The database has no other skills named treeship-session.

Database snapshot: 13.11.2026 · package version 38adf7d4811d (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100treeship-report
    Use when the user asks for "the URL", "a shareable link", "the proof I can send to <someone>", or otherwise wants the current Treeship session published as a session report on treeship.dev.
  • 100treeship-graph-loop
    Run bounded, spec-first implementation cycles for Treeship's workflow and graph proof layer. Use when continuing workflow declarations, checkpoint composition, run binding, evidence-derived paths, bounded loops, or conformance verification.
  • 82session-end
    Close a working session on Fairmark cleanly — run the quality gate, write the journal entry, add the release note fragment, commit, push and open or update the pull request with a complete, professional description. Use when the maintainer says the session is over, or before…
  • 82session-end
    Close a working session on Fairmark cleanly — run the quality gate, write the journal entry, add the release note fragment, commit, push and open or update the pull request with a complete, professional description. Use when the maintainer says the session is over, or before…
  • 100ship
    Use when work is done and you need to commit, push, close beads, and sync in one shot. The quick session-close ceremony.
  • 100close-session
    End-of-session close-out for a repository shared by several AI agents: commit this session's work with the Agent trailer, write or update today's log, paste the worklog line, release the board claim, and leave nothing of ours uncommitted. Use this whenever the user says wrap up,…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.