@staff0rd/assist 0.426.1 → 0.428.0

package/README.md

@@ -165,7 +165,8 @@ Backlog item ids are written and displayed in an `a`-prefixed form (e.g. item 55
 - `assist backlog import [file]` - Restore every table present in a dump (file or stdin) back into the backlog database in foreign-key-safe order, faithfully replacing all data and resyncing identity sequences; prompts for confirmation (use `-y, --yes` to skip; required when reading from stdin)
 - `assist backlog associate-jira <id> [key]` - Associate a Jira ticket with a backlog item; accepts a bare key (`PROJ-123`) or an Atlassian browse URL, validates the key shape, fetches the issue to confirm it exists, and stores the key (re-running with a different key replaces it). Clears any GitHub issue on the item (one external tracker per item). Use `--clear` to remove the association
 - `assist backlog associate-github <id> [issue]` - Associate a GitHub issue with a backlog item; accepts a full issue URL or `owner/repo#number` shorthand, normalises to `owner/repo#number`, and fetches the issue title via the `gh` CLI to confirm it. Clears any Jira key on the item (one external tracker per item). Use `--clear` to remove the association
-- `assist backlog add-activity <id> <kind> <ref>` - Attach a git activity ref to a backlog item, where `kind` is `branch`, `commit`, or `pr`; `branch`/`commit` auto-fill their GitHub URL. Use `--title`, `--url`, `--state` to supply or override metadata. Re-adding the same kind and ref upserts rather than duplicating
+- `assist backlog add-activity <id> <kind> <ref>` - Attach an activity ref to a backlog item, where `kind` is `branch`, `commit`, `pr`, or `slack`; `branch`/`commit` auto-fill their GitHub URL. Use `--title`, `--url`, `--state` to supply or override metadata. Re-adding the same kind and ref upserts rather than duplicating
+- `assist backlog record-slack <url>` - Attach a Slack thread permalink to the current session's backlog item (resolved from `ASSIST_BACKLOG_ITEM_ID`) as a `slack` activity ref; used by `/prs-slack` after posting. Use `--title` to label the ref with the PR title. Re-recording the same permalink upserts rather than duplicating, and outside a backlog session it is a silent no-op
 - `assist backlog move-repo <old-origin> [new-origin]` - Retag all items from one origin to another after a repo rename; the new origin defaults to the current repo's remote, both accept URL or `git@` forms, and a bare repo name works for the old origin when unambiguous. Prompts for confirmation (use `-y, --yes` to skip)
 - `assist backlog clone <origin>` - Clone a repo over SSH into the configured base directory (`clone.baseDir`, default `~/git`), deriving the SSH remote from a stored origin (`host/org/repo` -> `git@host:org/repo.git`) and cloning into `<base-dir>/<repo>`; `local:` origins have no remote and are not clonable
 - `assist backlog web [-p, --port <number>] [--no-open]` - Open the backlog tab in the web dashboard (default port 3100); `--no-open` skips opening a browser on startup

package/claude/commands/bug.md

@@ -71,7 +71,7 @@ Note the created item id from the output — you'll pass it to the done signal b
 
 ### Associate an external tracker
 
-If the user's original input (`$ARGUMENTS`) referenced an external tracker, associate it with the created item so downstream sessions have the context. Detect at most **one** tracker:
+If an external tracker was referenced anywhere in the conversation leading to this bug — whether in `$ARGUMENTS` or supplied at any point during the discussion — associate it with the created item so downstream sessions have the context. Detect at most **one** tracker:
 
 - A **Jira** issue — a bare key (`PROJ-123`) or an Atlassian browse URL (`https://<site>.atlassian.net/browse/PROJ-123`):
 
@@ -85,7 +85,17 @@ If the user's original input (`$ARGUMENTS`) referenced an external tracker, asso
   assist backlog associate-github a<id> "<issue-or-url>" 2>&1
   ```
 
-Only one external tracker can be set per item (associating one clears the other), so run at most one of these. If the input referenced no tracker, skip this step. If the association command reports an error (malformed reference, issue not found), relay it to the user but do not treat it as fatal — the item was still created successfully.
+Only one external tracker can be set per item (associating one clears the other), so run at most one of these. If no tracker was referenced, skip this step. If the association command reports an error (malformed reference, issue not found), relay it to the user but do not treat it as fatal — the item was still created successfully.
+
+### Attach a referenced Slack thread
+
+If a Slack thread was referenced anywhere in the conversation leading to this bug — a `slack.com` archives/permalink URL (e.g. `https://<workspace>.slack.com/archives/C.../p...`), whether in `$ARGUMENTS` or supplied at any point during the discussion — attach it to the created item so it renders as a linked Slack row in the Activity section:
+
+```
+assist backlog add-activity a<id> slack "<permalink>" --url "<permalink>" --title "Bug title" 2>&1
+```
+
+Use the same permalink verbatim for both the ref and `--url`, and the item's name for `--title`. If no Slack thread was referenced, skip this step.
 
 Then show the user the item was created and suggest they can run `assist backlog run a<id>` to start implementation.
 

package/claude/commands/draft.md

@@ -107,7 +107,7 @@ assist backlog add-phase a<id> "Phase name" --task "Task 1" --task "Task 2" --ma
 
 ### Associate an external tracker
 
-If the user's original input (`$ARGUMENTS`) referenced an external tracker, associate it with the created item so downstream sessions have the context. Detect at most **one** tracker:
+If an external tracker was referenced anywhere in the conversation leading to this item — whether in `$ARGUMENTS` or supplied at any point during the discussion — associate it with the created item so downstream sessions have the context. Detect at most **one** tracker:
 
 - A **Jira** issue — a bare key (`PROJ-123`) or an Atlassian browse URL (`https://<site>.atlassian.net/browse/PROJ-123`):
 
@@ -121,7 +121,17 @@ If the user's original input (`$ARGUMENTS`) referenced an external tracker, asso
   assist backlog associate-github a<id> "<issue-or-url>" 2>&1
   ```
 
-Only one external tracker can be set per item (associating one clears the other), so run at most one of these. If the input referenced no tracker, skip this step. If the association command reports an error (malformed reference, issue not found), relay it to the user but do not treat it as fatal — the item was still created successfully.
+Only one external tracker can be set per item (associating one clears the other), so run at most one of these. If no tracker was referenced, skip this step. If the association command reports an error (malformed reference, issue not found), relay it to the user but do not treat it as fatal — the item was still created successfully.
+
+### Attach a referenced Slack thread
+
+If a Slack thread was referenced anywhere in the conversation leading to this item — a `slack.com` archives/permalink URL (e.g. `https://<workspace>.slack.com/archives/C.../p...`), whether in `$ARGUMENTS` or supplied at any point during the discussion — attach it to the created item so it renders as a linked Slack row in the Activity section:
+
+```
+assist backlog add-activity a<id> slack "<permalink>" --url "<permalink>" --title "Item name" 2>&1
+```
+
+Use the same permalink verbatim for both the ref and `--url`, and the item's name for `--title`. If no Slack thread was referenced, skip this step.
 
 Then show the user the item was created and suggest they can run `assist backlog run a<id>` to start implementation.
 

package/claude/commands/prs-slack.md

@@ -9,3 +9,4 @@ Post pull request `$ARGUMENTS` to the configured Slack channel.
 3. Build the message `PR: [<title>](<url>)` using the fetched title and url.
 4. Show the user the resolved channel and the exact message, and confirm via `AskUserQuestion` before posting.
 5. On confirmation, resolve the channel name to its ID with `mcp__claude_ai_Slack__slack_search_channels`, then post the message to that channel with `mcp__claude_ai_Slack__slack_send_message`.
+6. Capture the message permalink returned by `slack_send_message` and record it against the session's backlog item with `assist backlog record-slack "<permalink>" --title "<title>"` (using the PR title from step 2). Outside a backlog session this is a silent no-op.