@grum-os/cli 0.3.52 → 0.3.54
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 +22 -7
- package/content.md5 +1 -1
- package/grum.mjs +604 -390
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -16,12 +16,13 @@ Open a terminal in the repository, and run with no arguments:
|
|
|
16
16
|
npx @grum-os/cli
|
|
17
17
|
```
|
|
18
18
|
|
|
19
|
-
Grum opens a wizard. The arrow keys move, Enter selects, and 1
|
|
19
|
+
Grum opens a wizard. The arrow keys move, Enter selects, and 1 to 4 jump straight to a row. `q` quits the menu. After you pick a row, `c` cancels that command and returns to the menu.
|
|
20
20
|
|
|
21
21
|
```text
|
|
22
|
-
1
|
|
23
|
-
2
|
|
24
|
-
3
|
|
22
|
+
1 Check Check your changes against the design contract
|
|
23
|
+
2 Quick wins Pick and run the latest scan's quick wins
|
|
24
|
+
3 Setup Sign in, link this repository, set up Cursor
|
|
25
|
+
4 Login Sign in to Grum
|
|
25
26
|
```
|
|
26
27
|
|
|
27
28
|
Choose **setup**. Grum walks through the rest:
|
|
@@ -32,11 +33,24 @@ Choose **setup**. Grum walks through the rest:
|
|
|
32
33
|
|
|
33
34
|
Then choose **check**. New drift is listed with a one-line fix, and Grum offers to send each item for review. You do not need to type a command for any of that.
|
|
34
35
|
|
|
35
|
-
Once you are signed in, the
|
|
36
|
+
Once you are signed in, the last row is **Logout**. Run `grum` again and choose **setup** to change the link or turn Cursor off. Enter keeps each current setting.
|
|
36
37
|
|
|
37
38
|
## Rescan a workspace
|
|
38
39
|
|
|
39
|
-
After changing code, run `grum scan` in the linked repository to start a fresh server-side scan and follow its progress in the terminal. Add `--root <dir>` when the workspace is a folder inside a monorepo. The scan runs in Grum and may take a few minutes. Ctrl+C stops waiting, but the scan keeps running. Only workspace owners can start scans.
|
|
40
|
+
After changing code, run `grum scan` in the linked repository to start a fresh server-side scan and follow its progress in the terminal. Add `--root <dir>` when the workspace is a folder inside a monorepo. The scan runs in Grum and may take a few minutes. Ctrl+C stops waiting, but the scan keeps running. Only workspace owners can start scans. When the scan finishes, Grum lists its [quick wins](#quick-wins).
|
|
41
|
+
|
|
42
|
+
## Quick wins
|
|
43
|
+
|
|
44
|
+
After setup and after each scan, Grum lists a few quick wins: the changes from the latest scan that make the biggest difference with little effort, such as missing design guidelines or hand-typed values that already match a token. They are the same items as the Quick wins list in Grum, without the ones your team dismissed there.
|
|
45
|
+
|
|
46
|
+
Choose **quick wins** in the menu (or run `grum wins`) to pick which ones to do, then where to send them: Claude Code or Codex start right there with the prompt, Cursor opens with it in the chat box, or copy or print it. Several picks go as one prompt, done one at a time. When one holds a draft (for example, when to use each button style), the agent shows it to you to correct first.
|
|
47
|
+
|
|
48
|
+
```sh
|
|
49
|
+
grum wins # pick and send them
|
|
50
|
+
grum wins 2 # print the prompt for the second one
|
|
51
|
+
```
|
|
52
|
+
|
|
53
|
+
In Claude Code and Cursor, type `/quick-wins`, or just ask for "quick wins". Codex has no project commands, so ask it for "quick wins". The agent shows the list and asks which ones to do.
|
|
40
54
|
|
|
41
55
|
## Set up with your agent
|
|
42
56
|
|
|
@@ -191,7 +205,7 @@ Clears the capture-browser sign-in saved for this repository.
|
|
|
191
205
|
grum contract
|
|
192
206
|
```
|
|
193
207
|
|
|
194
|
-
Prints the contract packet agents read before writing UI: tokens by category (with a separate dark value when there is one), button components and looks, approved text inputs, checkboxes, radios, switches, selects, action menus and tabs, team guidelines, and review decisions.
|
|
208
|
+
Prints the contract packet agents read before writing UI: tokens by category (with a separate dark value when there is one), button components and looks, approved text inputs, checkboxes, radios, switches, selects, action menus and tabs, team guidelines, quick wins, and review decisions.
|
|
195
209
|
|
|
196
210
|
## Fail the check
|
|
197
211
|
|
|
@@ -264,6 +278,7 @@ The menu covers check, setup, and sign-in. These are the same actions as flags,
|
|
|
264
278
|
| `grum uninstall [--yes]` | Remove Grum from this repository and this computer. See [Uninstall](#uninstall). |
|
|
265
279
|
| `grum capture reset` | Clear this repository's saved capture-browser sign-ins. |
|
|
266
280
|
| `grum contract` | Print the contract packet. |
|
|
281
|
+
| `grum wins [<number>]` | Pick quick wins and send them to your agent, or print one's prompt. See [Quick wins](#quick-wins). |
|
|
267
282
|
| `grum feedback "<what happened>" [--kind <kind>]` | Tell the Grum team about a question, confusion or problem. `<kind>` is `question`, `confused`, `problem` or `idea`. If Grum can't be reached it waits and goes with the next send. |
|
|
268
283
|
| `grum init cursor [--remove] [--force] [--local-only] [--pre-commit]` | Write or remove the Cursor files without the menu. `--pre-commit` adds the commit check. `--no-pre-commit` removes it. |
|
|
269
284
|
| `grum init codex [--remove] [--force] [--local-only] [--pre-commit]` | The same for Codex: `.codex/config.toml`, `.codex/hooks.json` and the `AGENTS.md` block. |
|
package/content.md5
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
|
|
1
|
+
cc40b2cacdeebea4dfdf1a63e6ffc8a6
|