@staff0rd/assist 0.717.0 → 0.719.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -59,6 +59,7 @@ After installation, the `assist` command will be available globally. You can als
59
59
  - `/refactor` - Run refactoring checks for code quality
60
60
  - `/prompts` - Analyze denied tool calls and suggest settings changes to auto-allow recurring prompts
61
61
  - `/recall` - Recall the most recent handover note for this repo
62
+ - `/run-logs [session-id|group]` - Read a run session's output via `assist sessions output` — a session id, or else a server group (default `default`) for this repo — and summarise its errors and relevant lines
62
63
  - `/releases-configure` - Set this repo's release promotion topology: read its workflow files, follow every `uses:` reusable-workflow call to whatever depth it nests, flatten the `needs:` graph across those boundaries into nodes and edges, put the graph to the user to accept or edit, then write it with `assist releases configure --streams ...` to the project `assist.yml` or this repo's block in `~/.assist.yml`. The repo is the one you are in — it is never passed
63
64
  - `/refine` - Refine an existing backlog item through conversation
64
65
  - `/rename [title]` - Retitle this session's dashboard card via `assist sessions rename`; uses the argument verbatim, or infers a short title from the conversation when given none
@@ -107,7 +108,7 @@ Every command supports `--help` for full detail on its flags and behaviour.
107
108
 
108
109
  ### Git and GitHub
109
110
 
110
- - `assist sync [--prune] [--force]` - Copy commands, settings and design assets to `~/.claude` (plus `~/.codex` and `~/.pi` when those CLIs are on PATH). No global instructions file is written any more — `~/.claude/CLAUDE.md`, `~/.codex/AGENTS.md` and `~/.pi/agent/AGENTS.md` are all gone, and each harness instead receives the repo's composed advice at session start: Claude Code from the `assist advise --hook` SessionStart hook, Codex from `assist codex-hook` on its `SessionStart` event, and pi from the `assist-advice.ts` extension. Any of those three files an earlier sync left on disk is named on every run — sync never deletes them, since a hand-written one is indistinguishable from a leftover, but until they go they keep injecting the retired global instructions. With `--prune`, also lists commands in the target dirs that sync did not write — anything whose name is not in the repo's `claude/commands/*.md` set — and adding `--force` removes them. `~/.codex/skills` and `~/.pi/agent/prompts` are only inspected when those CLIs are detected; an orphaned codex skill directory is removed only when `SKILL.md` is its sole content, and any other is left in place with a reason. Subdirectories and non-`.md` files are listed separately and never removed. `--force` without `--prune` is an error
111
+ - `assist sync [--prune] [--force]` - Copy commands, settings and design assets to `~/.claude` (plus `~/.codex` and `~/.pi` when those CLIs are on PATH). A command whose frontmatter sets `skill: true` is written to `~/.claude/skills/<name>/SKILL.md` instead of `~/.claude/commands/<name>.md` (any old `commands/<name>.md` is deleted, and a symlinked `SKILL.md` is replaced rather than written through), so it takes precedence over a project skill of the same name; `/pr` opts in. No global instructions file is written any more — `~/.claude/CLAUDE.md`, `~/.codex/AGENTS.md` and `~/.pi/agent/AGENTS.md` are all gone, and each harness instead receives the repo's composed advice at session start: Claude Code from the `assist advise --hook` SessionStart hook, Codex from `assist codex-hook` on its `SessionStart` event, and pi from the `assist-advice.ts` extension. Any of those three files an earlier sync left on disk is named on every run — sync never deletes them, since a hand-written one is indistinguishable from a leftover, but until they go they keep injecting the retired global instructions. With `--prune`, also lists commands in the target dirs that sync did not write — anything whose name is not in the repo's `claude/commands/*.md` set — and adding `--force` removes them. `~/.codex/skills` and `~/.pi/agent/prompts` are only inspected when those CLIs are detected; an orphaned codex skill directory is removed only when `SKILL.md` is its sole content, and any other is left in place with a reason. Subdirectories and non-`.md` files are listed separately and never removed. `--force` without `--prune` is an error
111
112
  - `assist activity [--since <date>]` - Chart GitHub commit activity per day (defaults to last 30 days)
112
113
  - `assist commit status` - Show git status and diff
113
114
  - `assist commit <message> [files...] [--ref <ref>]` - Stage files and create a git commit with validation. The message must be a single line under 50 characters; `--ref` is the only way to give the commit a body. Each `--ref` value is free text containing a URL (e.g. `--ref "rationale for removing it https://…"`) and becomes one `Ref:` trailer line, verbatim — commas are not separators, so repeat the flag to pass several. A value carrying no `http`/`https` URL is rejected before anything is staged
@@ -386,7 +387,7 @@ The Config tab of the sessions web dashboard never receives secret values: `GET
386
387
  - `assist sessions summarise [-f, --force] [-n, --limit <count>]` - Generate one-line summaries for unsummarised Claude sessions
387
388
  - `assist sessions close` - Dismiss the current daemon-managed session: kills its process tree, removes its card from the dashboard and reaps its worktree. Outside such a session it reports there is nothing to close and exits 0
388
389
  - `assist sessions rename <title>` - Retitle the current daemon-managed session: the given title replaces the generated title and the backlog item name on its dashboard card for the rest of its life. Outside such a session it reports there is nothing to rename and exits 0
389
- - `assist sessions output <session-id> [-n, --lines <count>]` - Print the last lines (default 200) of a session's output from the daemon's in-memory scrollback, ANSI codes stripped, then exit. Only sessions on this node; a `<node>:<id>` id, an unknown id or no running daemon prints an error and exits 1
390
+ - `assist sessions output [session-id] [--server [group]] [-n, --lines <count>]` - Print the last lines (default 200) of a session's output from the daemon's in-memory scrollback, ANSI codes stripped, then exit. `--server [group]` (group defaults to `default`) reads the live server run for the current repo's remote and group instead of taking an id. Only sessions on this node; a `<node>:<id>` id, an unknown id, no live server run or no running daemon prints an error and exits 1
390
391
  - `assist sessions nodes [--json]` - List this node and every linked node with its link state (see [Linked nodes](#linked-nodes))
391
392
  - `assist sessions nodes link <name> [url] [--ssh <alias> --port <port>] [--local-port <port>]` - Link a peer node by its web server URL, or over an ssh tunnel
392
393
  - `assist sessions nodes unlink <name>` - Remove a linked node
@@ -1,5 +1,6 @@
1
1
  ---
2
2
  description: Raise a PR with a concise description
3
+ skill: true
3
4
  ---
4
5
 
5
6
  Run `assist prs raise --help` and follow its guidance exactly to compose and raise the pull request for the current branch. The help text is authoritative — it covers the section options, how to pitch each section, and whether to confirm the title and body in the terminal or leave that to the web UI. Do not use `gh pr create` directly.
@@ -0,0 +1,29 @@
1
+ ---
2
+ description: Read a run session's output (e.g. a dev server) and summarise it
3
+ ---
4
+
5
+ Read the output of a run session on this node and summarise it for the task at hand.
6
+
7
+ ## Step 1: Pick the target
8
+
9
+ Look at `$ARGUMENTS`:
10
+
11
+ - **Empty** — the default server group: `assist sessions output --server`
12
+ - **Looks like a session id** (all digits, or `<node>:<digits>`) — `assist sessions output <id>`
13
+ - **Anything else** — a server group name: `assist sessions output --server <group>`
14
+
15
+ Add `-n <count>` if more than the default 200 lines is needed (e.g. the relevant error scrolled further back).
16
+
17
+ ## Step 2: Run it
18
+
19
+ Run the chosen command with `2>&1`. On exit 1 it prints why (no daemon, unknown session, no live server for this repo and group, linked-node session) — report that message and stop.
20
+
21
+ ## Step 3: Summarise
22
+
23
+ Do not echo the whole output. Report:
24
+
25
+ - Errors, stack traces and warnings, quoted verbatim with their surrounding lines
26
+ - The run's current state (e.g. listening on a port, compiling, crashed)
27
+ - Any lines relevant to what the conversation is working on
28
+
29
+ If nothing notable is there, say so in one line.