@staff0rd/assist 0.652.0 → 0.654.0

package/README.md

@@ -270,6 +270,7 @@ The Config tab of the sessions web dashboard never receives secret values: `GET
 - `assist code-comment confirm <pin>` - Insert the pinned comment at its file/line and clear the pin state
 - `assist db-migration unlock` - Page a human to approve creating the next new migration module, issuing a pin via desktop notification
 - `assist db-migration confirm <pin>` - Confirm a pin from `db-migration unlock`, letting that migration's file write through once
+- `assist advise [--hook]` - Print the advice fragments from `claude/advice/*.md` that apply to the cwd's repo, each selected by its `when` condition against the merged config and repo facts, composed in filename order. `--hook` reads the SessionStart payload from stdin for the session's cwd and emits the markdown as `hookSpecificOutput.additionalContext`
 - `assist notify` - Show desktop notification from JSON stdin (macOS, Windows, WSL)
 - `assist status-line` - Format Claude Code status line from JSON stdin
 
@@ -440,6 +441,7 @@ A restart kills every managed session's pty, which also kills any background tas
 - `prs.slack` — the Slack channel (e.g. `#example`) that `/prs-slack` posts pull requests to via the Slack MCP connector
 - `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.promptGithub` — when `true` (default `false`), the `assist prs raise --help` `--resolves` guidance instructs asking the user for a GitHub issue (`#123`, `owner/repo#123`, or a github.com issue URL). With `prs.promptJira` also `true` the guidance asks for either, and a mixed `--resolves` list renders each value in its own form
 - `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
 - `readTime.wordsPerMinute` — nominal prose reading speed (default `200`) that `assist read-time` estimates with. The effective rate decays with document length, fitted to timed readings of real documents: ~88 wpm at 129 words, ~70 wpm at 485. Fenced code is scored at half the prose rate
 - `prs.readingWordsPerMinute` — the same speed under the command's former name, read only when `readTime.wordsPerMinute` is unset

package/claude/advice/assist-global.md

@@ -0,0 +1,6 @@
+---
+title: Using assist
+when: always
+---
+
+`assist` is installed globally. Use it directly (e.g., `assist commit "message"`).

package/claude/advice/backlog-ids.md

@@ -0,0 +1,6 @@
+---
+title: Backlog item IDs
+when: always
+---
+
+A bare `a` followed by hex (e.g. `a791`, `a3f0`) is an assist backlog item ID, not a git SHA. Read it with `assist backlog view <id>`.

package/claude/advice/backlog-prs.md

@@ -0,0 +1,6 @@
+---
+title: Backlog items, PRs, and commits
+when: always
+---
+
+Do not mention assist backlog items in PR descriptions or PR comments. The reference goes the other way: mention the relevant commits or PRs in the assist backlog item.

package/claude/advice/code-comments.md

@@ -0,0 +1,6 @@
+---
+title: Commenting code
+when: always
+---
+
+Do not include comments for standard logic or syntax. Only comment if the specific line involves unintuitive complexity or a hack.

package/claude/advice/drafting-messages.md

@@ -0,0 +1,6 @@
+---
+title: Drafting messages to send on the user's behalf
+when: always
+---
+
+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.

package/claude/advice/editing-files.md

@@ -0,0 +1,6 @@
+---
+title: Editing files
+when: always
+---
+
+Always edit files with the Write and Edit tools. Never edit a file by shelling out — no `sed -i`, no heredoc rewrites, no Python or Node scripts that write the file. This overrides any session instruction that says to prefer Bash for file changes.

package/claude/advice/jira-context.md

@@ -0,0 +1,6 @@
+---
+title: Fetching Jira context
+when: jira
+---
+
+When the user mentions a Jira issue key (e.g. `BAD-671`, `PROJ-123`), use the Atlassian MCP to fetch context.

package/claude/advice/jira-smart-links.md

@@ -0,0 +1,6 @@
+---
+title: Editing Jira issues with Smart Links
+when: jira
+---
+
+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.

package/claude/advice/markdown.md

@@ -0,0 +1,6 @@
+---
+title: Writing markdown
+when: always
+---
+
+Do not hard-wrap markdown. One line per paragraph, per bullet, per heading — let it soft-wrap. Never break a line at some column width.

package/claude/settings.json

@@ -39,7 +39,10 @@
 		"SessionStart": [
 			{
 				"matcher": "",
-				"hooks": [{ "type": "command", "command": "assist handover load" }]
+				"hooks": [
+					{ "type": "command", "command": "assist handover load" },
+					{ "type": "command", "command": "assist advise --hook" }
+				]
 			}
 		]
 	},