@staff0rd/assist 0.381.0 → 0.382.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.
- package/claude/CLAUDE.md +4 -0
- package/dist/commands/sessions/web/bundle.js +72 -72
- package/dist/index.js +482 -305
- package/package.json +2 -10
package/claude/CLAUDE.md
CHANGED
|
@@ -20,6 +20,10 @@ When the user mentions a Jira issue key (e.g. `BAD-671`, `PROJ-123`), use the At
|
|
|
20
20
|
|
|
21
21
|
When editing a Jira issue whose description (or comment) contains Smart Links — rendered issue-key/URL chips, stored as ADF `inlineCard` nodes — edit via `editJiraIssue` with `contentFormat: "adf"` and emit real `inlineCard` nodes. Never round-trip such content through `contentFormat: "markdown"`: markdown has no representation for `inlineCard`, so every existing Smart Link is flattened to a plain browse URL and lost. Jira does not auto-promote plain browse URLs back into Smart Links, so the damage is not self-healing. Inspect the current stored ADF first and preserve existing `inlineCard` nodes when making a small edit. For anything beyond a trivial edit, build the ADF programmatically (a small script) rather than hand-authoring it inline — full-description ADF is verbose and easy to get wrong.
|
|
22
22
|
|
|
23
|
+
## Drafting messages to send on the user's behalf
|
|
24
|
+
|
|
25
|
+
When drafting a message to send on the user's behalf (Slack, PR, email, comment): state only the confirmed conclusion and the facts behind it. No hedging, no speculative next-steps, no fixes not agreed to, no pleasantries. Match the scope of what was asked — nothing added.
|
|
26
|
+
|
|
23
27
|
## Commenting code
|
|
24
28
|
|
|
25
29
|
Do not include comments for standard logic or syntax. Only comment if the specific line involves unintuitive complexity or a hack.
|