@staff0rd/assist 0.427.0 → 0.428.1

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.
Files changed (5) hide show
  1. package/claude/commands/bug.md +12 -2
  2. package/claude/commands/draft.md +12 -2
  3. package/dist/commands/sessions/web/bundle.js +384 -384
  4. package/dist/index.js +1 -1
  5. package/package.json +1 -1
package/claude/commands/bug.md CHANGED
@@ -71,7 +71,7 @@ Note the created item id from the output — you'll pass it to the done signal b
71
71
 
72
72
  ### Associate an external tracker
73
73
 
74
- 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:
74
+ 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:
75
75
 
76
76
  - A **Jira** issue — a bare key (`PROJ-123`) or an Atlassian browse URL (`https://<site>.atlassian.net/browse/PROJ-123`):
77
77
 
@@ -85,7 +85,17 @@ If the user's original input (`$ARGUMENTS`) referenced an external tracker, asso
85
85
  assist backlog associate-github a<id> "<issue-or-url>" 2>&1
86
86
  ```
87
87
 
88
- 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.
88
+ 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.
89
+
90
+ ### Attach a referenced Slack thread
91
+
92
+ 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:
93
+
94
+ ```
95
+ assist backlog add-activity a<id> slack "<permalink>" --url "<permalink>" --title "Bug title" 2>&1
96
+ ```
97
+
98
+ 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.
89
99
 
90
100
  Then show the user the item was created and suggest they can run `assist backlog run a<id>` to start implementation.
91
101
 
package/claude/commands/draft.md CHANGED
@@ -107,7 +107,7 @@ assist backlog add-phase a<id> "Phase name" --task "Task 1" --task "Task 2" --ma
107
107
 
108
108
  ### Associate an external tracker
109
109
 
110
- 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:
110
+ 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:
111
111
 
112
112
  - A **Jira** issue — a bare key (`PROJ-123`) or an Atlassian browse URL (`https://<site>.atlassian.net/browse/PROJ-123`):
113
113
 
@@ -121,7 +121,17 @@ If the user's original input (`$ARGUMENTS`) referenced an external tracker, asso
121
121
  assist backlog associate-github a<id> "<issue-or-url>" 2>&1
122
122
  ```
123
123
 
124
- 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.
124
+ 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.
125
+
126
+ ### Attach a referenced Slack thread
127
+
128
+ 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:
129
+
130
+ ```
131
+ assist backlog add-activity a<id> slack "<permalink>" --url "<permalink>" --title "Item name" 2>&1
132
+ ```
133
+
134
+ 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.
125
135
 
126
136
  Then show the user the item was created and suggest they can run `assist backlog run a<id>` to start implementation.
127
137