@staff0rd/assist 0.577.0 → 0.579.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 +2 -2
- package/dist/commands/sessions/web/bundle.js +395 -395
- package/dist/index.js +885 -697
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -136,7 +136,7 @@ Every command supports `--help` for full detail on its flags and behaviour.
|
|
|
136
136
|
- `assist github issue create --title <title> --body <body> [-R <owner>/<repo>]` - Create a GitHub issue on the current repo (or `-R`'s). There is no What/Why/How template — an issue reports a problem, and the target repo's own issue template is unknowable from here. The title and body are rejected if they reference Claude or an assist backlog item, and in a web session they are previewed for approve/reject first (with inline comments); nothing is created until it is approved. Raw `gh issue create` is denied in favour of this command
|
|
137
137
|
- `assist github issue edit <number> [-R <owner>/<repo>] [--fresh]` - Rework an existing GitHub issue's body in the web preview pane. Fetches the issue's current `title`, `body` and `updatedAt` with `gh issue view`, writes the body to a working file under `~/.assist/github-issues/`, and previews it for approve/reject. Approving pushes the pane's markdown back with `gh issue edit --body-file`; nothing is pushed if the issue was updated on GitHub after it was fetched (the working file is named instead, so nobody else's edit is clobbered) or if the preview is rejected. Rejecting writes the pane's markdown — collapses included — to the working file and names it in the output, so the revision is made in that file rather than composed from scratch; a re-run resumes from the working file while the issue has not moved on GitHub, and `--fresh` discards it and re-fetches. Outside a web session there is no pane to edit in, so the command just prints the issue — callers never need to detect the session themselves. Only the body is touched — the title, labels, assignees and state are left alone
|
|
138
138
|
- `assist github issue comment <number> --body <body> [-R <owner>/<repo>]` - Comment on a GitHub issue on the current repo (or `-R`'s); a body of `-` reads it from stdin. The body is rejected if it references Claude or an assist backlog item, and in a web session it is previewed for approve/reject first (with inline comments); nothing is posted until it is approved. Raw `gh issue comment` is denied in favour of this command
|
|
139
|
-
- `assist github issue fix-structure <target> [-R <owner>/<repo>] [--level epic|story|subtask]` -
|
|
139
|
+
- `assist github issue fix-structure <target> [-R <owner>/<repo>] [--level epic|story|subtask] [--apply]` - Normalise the issue types across one issue subtree, reading and writing nothing outside it. `<target>` is `owner/repo#number`, a github.com issue URL, or a bare number with `-R`; a bare number with no repo is refused rather than guessed. Walks the subtree via sub-issues level by level (a single deep query blows the GraphQL node limit) and reports the type each issue should carry: every level below the target is typed to the next level down the `Epic` > `Story` > `Subtask` chain, matching type names loosely so `Subtask` and `Sub-task` both bind to the leaf. Untyped issues are typed rather than skipped, and cross-repo children are handled in the one run. The target's own level is inferred from its issue type, so aiming at a story types its children as subtasks; when its type is not in the chain the level cannot be inferred and the command exits non-zero naming the type it has. `--level` asserts the position instead, which also types the target itself. Anything nested below the leaf level fails the run before a single write, naming the offender and its parent; nothing is ever re-parented. Without `--apply` nothing is written. `--apply` announces each write before it is issued and flushes it, so a long run shows progress, then re-walks the subtree and fails with a non-zero exit if any drift remains
|
|
140
140
|
- `assist news add [url]` - Add an RSS feed URL (rendered in the sessions web News tab)
|
|
141
141
|
|
|
142
142
|
### Backlog
|
|
@@ -274,7 +274,7 @@ The Config tab of the sessions web dashboard never receives secret values: `GET
|
|
|
274
274
|
- `assist jira ac <issue-key>` - Print acceptance criteria for a Jira issue
|
|
275
275
|
- `assist jira view <issue-key>` - Print the title and description of a Jira issue
|
|
276
276
|
- Note: Claude fetches Jira context via the MCP Atlassian server, so `/jira` and Jira-key mentions go through MCP. These CLI commands remain for direct human use.
|
|
277
|
-
- `assist miro extract --items <file> --top-left <id|link> --bottom-right <id|link
|
|
277
|
+
- `assist miro extract --items <file> [--top-left <id|link> --bottom-right <id|link>]` - Print the text of every box inside a rectangle on a Miro board as a YAML list, leftmost box edge first (topmost edge breaks ties). `--items` is a file of raw `board_list_items` response pages; anchors accept a bare widget id or a `?moveToWidget=<id>` link. Omit both anchors to pick them by clicking the top-left then the bottom-right box in the assist web UI preview pane, which echoes the pair back as flags for later runs
|
|
278
278
|
- `assist ravendb auth add` - Add a new RavenDB connection
|
|
279
279
|
- `assist ravendb auth list` - List configured RavenDB connections
|
|
280
280
|
- `assist ravendb auth remove <name>` - Remove a configured connection
|