@paxnax/berliner 0.5.3 → 0.6.0

package/skill/SKILL.md

@@ -28,6 +28,7 @@ Hooks installed by `berliner setup` already report the session's cost, model, re
 | `--pr` | Every pull request, one flag each. |
 | `--coverage` | Percent, from the test run's coverage summary. |
 | `--evidence` | Each screenshot or video. |
+| `--team`, `--no-team` | Only when the user asks for a one-off. See [Teams](#teams). |
 
 Do not pass `--session-id`, `--cost` or `--model`: the CLI fills them in from the tool's own records, and an explicit value is ignored with a warning. `--repo` and `--plan` are not needed either: the plan comes from the user's `BERLINER_PLAN`, or from their subscriptions in Settings. A report without `--title` keeps the session's existing title. `berliner update` ignores a session ID here.
 
@@ -86,6 +87,36 @@ In a non-interactive session (no user to answer), never ask and never save.
 
 The repository comes from `git remote get-url origin`; `--repo owner/name` names another one.
 
+## Teams
+
+A session reports to the user's own plan unless a team is set. The CLI picks the team from the first of these that exists:
+
+| Source | Use it for |
+|---|---|
+| `--team <uuid>` or `--no-team` | One report. `--no-team` beats every other source. |
+| `team` in `.berliner.json` at the repository root: `{ "team": "<uuid>" }` | The whole team. The file is meant to be committed. |
+| `BERLINER_TEAM` | One machine or shell. |
+| `berliner team <uuid>` | One machine, saved globally. `berliner team --none` clears it; `berliner team` prints the team in effect and where it came from. |
+
+With none of them, the session goes to the user's own plan. Do not set a team yourself: the user or the repository already did.
+
+Only the report that creates a session sends the team. A session's team is fixed after that, and the CLI warns when a later setting differs. Ignore the warning.
+
+The server can refuse the report that creates a team session with a 422. The message says how to fix it:
+
+| Code | Meaning | Fix |
+|---|---|---|
+| `team_not_found` | No team has that uuid. | Check the uuid in `.berliner.json`, `BERLINER_TEAM` or the global setting. |
+| `team_not_member` | The user is not a member of the team. | The user accepts the team's invite in the web app, or the owner invites them. |
+| `team_not_eligible` | The repository's owner is not an organization the team covers. | The team's owner adds the organization in the web app, or the user reports this repository without the team. |
+| `team_inactive` | The team has no active plan. | The team's owner sets up the plan in the web app. |
+
+When a report is refused, tell the user in your next message and quote the message the CLI printed. Inside Claude Code, Codex or OpenCode the hook cannot print it: it saves a note, and the next `berliner report`, `update`, `session` or `sessions` in that repository prints it once. The web app shows it as a banner too.
+
+Never add `--no-team` or a different `--team` just to get past a refusal unless the user agrees. That moves the session to another plan.
+
+The team's owner sees every session and file reported to the team. Members never see each other's team work.
+
 ## Keep PR states current
 
 A PR in a repository without the Berliner GitHub App keeps the state you last reported. So:
@@ -119,6 +150,7 @@ Report again with the same `--session-id` whenever something changes.
 - `--public`: with `--evidence`, also make those files viewable without sign-in. See below.
 - `--task <id>`, `--task-url <url>`: the ticket. See [Tickets](#tickets).
 - `--project <name>`: only the ticket's tracker project or a project the user named. See [Projects](#projects).
+- `--team <uuid>`, `--no-team`: which plan the session reports to. See [Teams](#teams).
 - `--started-at <ISO>`, `--ended-at <ISO>`.
 
 Quote any value that contains spaces.