@staff0rd/assist 0.610.0 → 0.611.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/README.md +1 -0
- package/claude/commands/rename.md +24 -0
- package/dist/commands/sessions/web/bundle.js +339 -339
- package/dist/index.js +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -59,6 +59,7 @@ After installation, the `assist` command will be available globally. You can als
|
|
|
59
59
|
- `/prompts` - Analyze denied tool calls and suggest settings changes to auto-allow recurring prompts
|
|
60
60
|
- `/recall` - Recall the most recent handover note for this repo
|
|
61
61
|
- `/refine` - Refine an existing backlog item through conversation
|
|
62
|
+
- `/rename [title]` - Retitle this session's dashboard card via `assist sessions rename`; uses the argument verbatim, or infers a short title from the conversation when given none
|
|
62
63
|
- `/restructure` - Analyze and restructure tightly-coupled files
|
|
63
64
|
- `/review-pr-comments` - Process PR review comments one by one
|
|
64
65
|
- `/jira [action] [KEY] [args]` - Jira actions: `view`, `associate`, `update`, `started`, `done`, `help`. `[KEY]` is optional — it resolves from the session's backlog item
|
|
@@ -0,0 +1,24 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Rename this session's dashboard card
|
|
3
|
+
allowed_args: "[title]"
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
Retitle the session this conversation is running in, so its dashboard card reads as something useful.
|
|
7
|
+
|
|
8
|
+
## Step 1: Decide the title
|
|
9
|
+
|
|
10
|
+
If `$ARGUMENTS` is non-empty, that text **is** the title — use it verbatim. Do not rewrite, expand, or capitalise it.
|
|
11
|
+
|
|
12
|
+
If `$ARGUMENTS` is empty, infer the title from this conversation: what the session is actually working on, as a short noun phrase of at most 48 characters (e.g. `fix login redirect`, `rename command phase 2`). Base it only on the conversation — do not run commands to investigate.
|
|
13
|
+
|
|
14
|
+
## Step 2: Apply it
|
|
15
|
+
|
|
16
|
+
```
|
|
17
|
+
assist sessions rename '<title>'
|
|
18
|
+
```
|
|
19
|
+
|
|
20
|
+
Use single quotes to avoid shell escaping issues. The rename is permanent for the life of the session: it beats both the generated title and the backlog item name, and renaming again is the only way to change it.
|
|
21
|
+
|
|
22
|
+
## Step 3: Report
|
|
23
|
+
|
|
24
|
+
Tell the user the new name in one line. If the command reports there is no daemon-managed session to rename, relay that instead.
|