@staff0rd/assist 0.963.0 → 0.965.0

package/README.md

@@ -150,7 +150,7 @@ Every command supports `--help` for full detail on its flags and behaviour.
   - `--checkout-only` - Skip the review; check the PR out and leave an idle Claude session in it. In a clone whose remote is on Azure DevOps it checks out with `az repos pr checkout` instead of `gh` (see [Azure DevOps PRs](#azure-devops-prs))
   - `--high-level` - Open the high-level review checklist in the web preview pane and post it to the PR as an Approve, Comment or Request changes review. Comments on lines selected in a diff or a test's source are either sent to the agent or added to the review, where those on lines in the PR diff post as line-level comments. See [docs/high-level-review.md](docs/high-level-review.md)
   - `--configure` - With `--high-level`: configure the checklist's `review.highLevel.*` keys instead of reviewing
-  - `--scope <repo|project>` - With `--configure`: write to this repo's override in the shared assist database or the project `assist.yml` instead of asking
+  - `--scope <db|git>` - With `--configure`: write to repo (db), this repo's override in the shared assist database, or repo (git), the repo's `assist.yml`, instead of asking
   - `--answer <key=value>` - With `--configure`: answer one key without prompting, repeatable; an empty value leaves the key unset
   - `--address-comments` - Start an Address Comments session for the PR once comments are posted and the review submitted
   - `--announce` - Announce the PR in Slack at the end of the chain
@@ -176,7 +176,7 @@ Every command supports `--help` for full detail on its flags and behaviour.
 - `assist news remove <url>` - Remove a feed URL from `news.feeds`
   - `news.feeds` - The feed URLs, stored in the assist database so every machine shares them; `assist config set news.feeds <url1>,<url2>` replaces the whole list
 - `assist releases [list]` - Print the release promotion streams declared in `releases.streams`
-- `assist releases configure --streams <file> [--scope <project|repo>]` - Write release streams from a JSON or YAML file (`-` for stdin) to `releases.streams`, in the project `assist.yml` (default) or this repo's shared override in the assist database
+- `assist releases configure --streams <file> [--scope <git|db>]` - Write release streams from a JSON or YAML file (`-` for stdin) to `releases.streams`, in repo (git), the repo's `assist.yml` (default), or repo (db), this repo's shared override in the assist database
 
 ### Backlog
 

package/claude/commands/releases-configure.md

@@ -35,8 +35,8 @@ A job with `uses: <owner>/<name>/.github/workflows/<file>@<ref>` calls a reusabl
 
 Show the nodes and edges you intend to write, and say which workflow file each node came from — including the reusable ones, so the user can see the chain you followed. Ask them to accept or edit, and ask which config file it goes to:
 
-- `project` — the repo's own `assist.yml`, checked in, so the team sees the same graph
-- `repo` — this repo's block in `~/.assist.yml`, personal to this machine
+- `git` — repo (git), the repo's own `assist.yml`, checked in, so the team sees the same graph
+- `db` — repo (db), this repo's override in the shared assist database, personal to the user and seen by every node
 
 Ask rather than guess: which jobs deserve a node at all, how jobs split into streams, what to call a stream, and any environment name that is computed rather than written literally.
 
@@ -45,7 +45,7 @@ Ask rather than guess: which jobs deserve a node at all, how jobs split into str
 Write the accepted streams to a JSON file and pass it in. Run the command from the repo you are in, never from another checkout: the config it writes belongs to the directory it runs in, whichever repos its streams point at. Set `repo` on any stream that releases another repo; one left out defaults to the repo you are in.
 
 ```
-assist releases configure --scope project --streams /tmp/streams.json
+assist releases configure --scope git --streams /tmp/streams.json
 ```
 
 ```json

package/claude/commands/review-config.md

@@ -35,8 +35,8 @@ Do not ask in chat. Write the proposal as markdown to a scratch file with the Wr
 - `descriptionWordCap` with its value
 - `collapsedPaths`, each glob as its own bullet like the others
 - the scope you propose, with the other one named so the user can swap it:
-  - `repo` — this repo's override in the shared assist database, personal to the user and seen by every node (propose this unless the user has said otherwise)
-  - `project` — the repo's own `assist.yml`, a file to check in so the team reviews against the same globs; only when the user asks for it, since it leaves a new file in a repo they may not own
+  - `db` — repo (db), this repo's override in the shared assist database, personal to the user and seen by every node (propose this unless the user has said otherwise)
+  - `git` — repo (git), the repo's own `assist.yml`, a file to check in so the team reviews against the same globs; only when the user asks for it, since it leaves a new file in a repo they may not own
 
 Then run, **as a background task**, doing no other work until it returns:
 
@@ -55,7 +55,7 @@ Outside a web session `assist ask` only prints the markdown and exits 0 without
 Pass every key, so nothing is prompted for — you have already asked:
 
 ```
-assist review --high-level --configure --scope repo \
+assist review --high-level --configure --scope db \
   --answer 'review.highLevel.criticalPaths=**/*.graphql,en-AU/translation.json' \
   --answer 'review.highLevel.uiPaths=src/ui/**' \
   --answer 'review.highLevel.descriptionWordCap=300' \