@staff0rd/assist 0.729.0 → 0.730.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
@@ -81,6 +81,7 @@ After installation, the `assist` command will be available globally. You can als
81
81
  - `/test-review` - Review existing tests for quality, coverage gaps, and conventions
82
82
  - `/inspect` - Run .NET code inspections on changed files
83
83
  - `/screenshot` - Capture a screenshot of a running application window
84
+ - `/show [what to show]` - Open long URLs, paths and snippets in the web preview pane via `assist show`, where the terminal's hard wrapping can't break them. With no arguments it gathers them from the previous reply
84
85
  - `/raven` - Query and manage RavenDB connections and collections
85
86
  - `/miro [board url | extract name]` - Dump a Miro frame's raw `board_list_items` pages and extract its boxes as an ordered YAML list via `assist miro extract`
86
87
  - `/seq` - Query Seq logs from a URL or filter expression
@@ -345,6 +346,7 @@ The Config tab of the sessions web dashboard never receives secret values: `GET
345
346
  - `assist mermaid export [file.md]` - Render each fenced mermaid block to `<stem>-<index>.svg` via [Kroki](https://kroki.io) (`--out`, `--index`, `mermaid.krokiUrl`)
346
347
  - `assist prompts` - Show top 10 denied tool calls by frequency with count and repo breakdown
347
348
  - `assist chart [--title <title>]` - Draw a terminal line chart of a `label value` series piped in on stdin, one pair per line, separated by a comma, tab or whitespace. Points are charted in the order given — nothing is sorted or aggregated — and the chart closes on q, Esc or Ctrl-C. The y axis fits the data range with 20% padding rather than starting at zero, so a series that only moves in its third decimal still reads as a shape; a flat series is padded so the line does not sit on the axis. Blank lines are skipped, fewer than two points prints `Not enough data points to chart.`, and a non-numeric value exits 1 naming the line
349
+ - `assist show --body <markdown|-> [--title <title>]` - Render markdown in the session's web preview pane so long links, paths and code can be clicked and copied unbroken; `--body -` reads it from stdin. It returns straight away and the pane stays open, with links opening in a new tab, until the user clicks Close. A later `show` replaces it. Outside a web session it prints the markdown to stdout
348
350
 
349
351
  ### Project setup
350
352
 
@@ -508,14 +510,13 @@ releases:
508
510
 
509
511
  ## Next
510
512
 
511
- The **Next** tab (`/next`) answers "what should I do next?" from the selected repo, across the GitHub repos that repo is configured to span. It lists open, non-draft PRs in any `next.prRepos` repo authored by a login in `next.peers` or requesting your review, hiding peer PRs you approved at their current head commit, ordered by your latest review request (or creation, for an unrequested peer PR), oldest first. Below them come open issues assigned to you in any `next.issueRepos` repo, oldest first. Both repo lists are `owner/name` and default to the selected repo; set them per repo with `-g --repo` so each repo's Next view spans its own set. The header shows the current peers and repos, with the command for any that is unset.
513
+ The **Next** tab (`/next`) answers "what should I do next?" from the selected repo, across the GitHub repos that repo is configured to span. `next.repos` lists the `owner/name` repos it reads, defaulting to the selected repo; set it per repo with `-g --repo` so each repo's Next view spans its own set. Across those repos it lists open, non-draft PRs authored by a login in `next.peers` or requesting your review, hiding peer PRs you approved at their current head commit, ordered by your latest review request (or creation, for an unrequested peer PR), oldest first. Below them come open issues assigned to you, oldest first. The header shows the current peers and repos, with the command for any that is unset.
512
514
 
513
515
  The top item (peer PRs before issues) is shown as a hero with a line explaining why it was chosen, and every item shows its `owner/name#number`. Every item has **Start session** and **GitHub**. Start session runs in the local clone of the item's repo (matched by origin among the repos the web app knows), and is disabled when there is none: on a PR it opens the same review type dialog as the toolbar `prs` dropdown; on an issue it opens the new-session dialog prefilled with the issue reference. Opening `/?new=<text>&newCwd=<path>` prefills the new-session prompt and repo the same way. A source that fails to load, or one of its repos that cannot be read, shows its error in its own section without hiding the rest. Data comes from `GET /api/next?cwd=<repo>`, with gh results cached for 30s.
514
516
 
515
517
  ```bash
516
518
  assist config set next.peers alice,bob -g --repo
517
- assist config set next.prRepos owner/api,owner/web -g --repo
518
- assist config set next.issueRepos owner/api,owner/web -g --repo
519
+ assist config set next.repos owner/api,owner/web -g --repo
519
520
  ```
520
521
 
521
522
  ## Parallel work
package/allowed.cli-reads CHANGED
@@ -64,6 +64,7 @@ assist sessions nodes
64
64
  assist sessions nodes doctor
65
65
  assist sessions nodes logs
66
66
  assist sessions output
67
+ assist show
67
68
  assist sql auth list
68
69
  assist sql columns
69
70
  assist sql query
@@ -0,0 +1,28 @@
1
+ ---
2
+ description: Open long links, paths and snippets in the web preview pane
3
+ allowed_args: "[what to show]"
4
+ ---
5
+
6
+ The terminal hard-wraps long lines, which breaks URLs, paths and snippets for clicking and copying. `assist show` renders markdown in the session's web preview pane instead, where they stay whole.
7
+
8
+ ## Step 1: compose the markdown
9
+
10
+ If `$ARGUMENTS` is non-empty, show what it describes.
11
+
12
+ If `$ARGUMENTS` is empty, gather every long URL, file path and code snippet from your previous reply. Leave out the surrounding prose. Keep each item verbatim and whole:
13
+
14
+ - URLs as markdown links or bare URLs, one per line
15
+ - paths in inline code
16
+ - snippets in fenced code blocks, with a language specifier where known
17
+
18
+ Give each item a short label saying what it is. If the previous reply has none, say so and stop.
19
+
20
+ Write the markdown to a scratch file with the Write tool. It will contain quotes, backticks and newlines, so don't inline it in a shell command.
21
+
22
+ ## Step 2: show it
23
+
24
+ ```
25
+ assist show --title '<short title>' --body - < <scratch file>
26
+ ```
27
+
28
+ The command returns straight away and the pane stays open until the user closes it. Outside a web session it prints the markdown instead. Either way, tell the user in one line what you showed.
@@ -64,6 +64,7 @@ assist sessions nodes
64
64
  assist sessions nodes doctor
65
65
  assist sessions nodes logs
66
66
  assist sessions output
67
+ assist show
67
68
  assist sql auth list
68
69
  assist sql columns
69
70
  assist sql query