@staff0rd/assist 0.629.1 → 0.630.1

package/README.md

@@ -114,7 +114,7 @@ Every command supports `--help` for full detail on its flags and behaviour.
 - `assist prs` - List pull requests for the current repository
 - `assist prs raise --title <t> --what <w> --why <y> [--how <h>] [--resolves <key>] [--force] [--draft|--no-draft]` - Raise a PR, assembling the body from What/Why/How. Whether the PR is created as a draft comes from `prs.draft` unless `--draft` or `--no-draft` is passed, which always wins. In a web session the draft is previewed for approve/reject (with inline comments and pasted screenshots, hosted via the [`gh-image`](https://github.com/drogers0/gh-image) gh extension) before the PR is created. The preview pane carries two independent chain checkboxes, both default on: **Review** chains a `review --no-prompt --submit <n> --address-comments` session once the PR is raised (review → post findings → Address Comments), and **Post** announces the PR in Slack at the tail of that chain — or directly via `/prs-slack <n> --no-confirm` when Review is off. With both on, approving runs raise → Review + Post → Address Comments → Slack announce end to end. A third checkbox, **Auto-merge (squash)**, defaults off and is offered for both a new PR and an update to an existing one: approving with it ticked runs `gh pr merge --auto --squash` on the current branch's PR once it is placed, before the chain runs, and a repo that refuses auto-merge only prints a warning. It and **Draft** untick each other, since GitHub refuses auto-merge on a draft PR
 - `assist prs edit [--title <t>] [--what <w>] [--why <y>] [--how <h>] [--resolves <key>]` - Update only the supplied sections of the current PR's body. In a web session the resulting title and body are previewed for approve/reject first (with inline comments and pasted screenshots, as for `raise`); on approval the edit is applied with any screenshots appended, on rejection the reviewer's comments are printed and nothing is changed. Outside a session the edit applies directly
-- `assist prs read-time <target> [--budget <duration>]` - Estimate how long a pull request description takes to read, printing e.g. `142 words · ~43s read`. `<target>` is a PR number, a GitHub PR URL (which may point at another repo), `-` to read the body from stdin, or a path to a file holding a draft body; the current branch's PR is deliberately not a default. Prose counts at `prs.readingWordsPerMinute` (default 200) and fenced code at half that, with a bare URL or an image/HTML tag counting as one word. When the estimate exceeds the budget — one minute unless `--budget` (`45s`, `1m30s`, `2m`) says otherwise — `· over the ~1m budget` is appended
+- `assist prs read-time <target> [--budget <duration>]` - Estimate how long a pull request description takes to read, printing e.g. `142 words · ~1m 25s read`. `<target>` is a PR number, a GitHub PR URL (which may point at another repo), `-` to read the body from stdin, or a path to a file holding a draft body; the current branch's PR is deliberately not a default. Prose counts at `prs.readingWordsPerMinute` (default 100) and fenced code at half that, with a bare URL or an image/HTML tag counting as one word. When the estimate exceeds the budget — one minute unless `--budget` (`45s`, `1m30s`, `2m`) says otherwise — `· over the ~1m budget` is appended
 - `assist prs list-comments` - List all comments on the current branch's pull request
 - `assist prs fixed <comment-id> <sha>` - Reply with commit link and resolve thread
 - `assist prs wontfix <comment-id> <reason>` - Reply with reason and resolve thread. In a web session the reason is previewed for approve/reject first (with inline comments); on rejection nothing is posted, the reviewer's comments are printed and the command exits non-zero. Pass `-` as the reason to read it from stdin. A body containing markdown — backticks around identifiers, `$(...)`, `$VAR` — must be piped in rather than passed as an argument, or the calling shell expands it before assist sees it:
@@ -439,7 +439,7 @@ A restart kills every managed session's pty, which also kills any background tas
 - `prs.required` — when `true` (default `false`), `assist backlog run` cuts and records a fresh branch for a story that has no recorded branch at run start, so a new story never inherits the previous one's branch
 - `prs.promptJira` — when `true` (default `false`), the `assist prs raise --help` `--resolves` guidance instructs asking the user for a Jira key
 - `prs.draft` — when `true` (default `false`), `assist prs raise` creates a draft PR. `--draft` and `--no-draft` override it in either direction; only the create path is affected, `assist prs edit` never changes an existing PR's draft state
-- `prs.readingWordsPerMinute` — prose reading speed (default `200`) that `assist prs read-time` estimates with; fenced code is scored at half that rate
+- `prs.readingWordsPerMinute` — prose reading speed (default `100`, measured against real pull request descriptions rather than the ~200 wpm of easy prose) that `assist prs read-time` estimates with; fenced code is scored at half that rate
 - `commit.pull` — when enabled, `assist draft`, `bug`, `refine`, `next` and `backlog run` run `git pull --ff-only` first and abort if it fails (`next` pulls once per invocation, not per item)
 - `commit.expectedBranch` — when set (e.g. `main`), `assist commit` prints a non-blocking warning if HEAD is on any other branch, so work on a stray branch isn't silently orphaned
 - `branch.prefix` — when set (e.g. `sw`), `assist branch <slug>` prepends `<prefix>/` to the branch name