getgloss 0.12.1 → 0.13.0

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 (16) hide show
  1. package/README.md +14 -6
  2. package/dist/cli/index.js +51 -9
  3. package/dist/cli/index.js.map +1 -1
  4. package/dist/server/daemon.js +173 -19
  5. package/dist/server/daemon.js.map +1 -1
  6. package/dist/web/assets/index-0IC9C6Wd.js +307 -0
  7. package/dist/web/assets/index-acdiHHul.css +1 -0
  8. package/dist/web/assets/{syntax-UR_bDbhr.js → syntax-CvRmtNgl.js} +1 -1
  9. package/dist/web/index.html +2 -2
  10. package/dist/web/prompt.md +3 -2
  11. package/dist/web/setup/index.html +5 -1
  12. package/dist/web/setup.md +8 -3
  13. package/package.json +3 -3
  14. package/skill/SKILL.md +2 -2
  15. package/dist/web/assets/index-BYtByjSm.js +0 -306
  16. package/dist/web/assets/index-Bn84l3Zr.css +0 -1
package/dist/web/index.html CHANGED
@@ -44,8 +44,8 @@
44
44
  }
45
45
  })();
46
46
  </script>
47
- <script type="module" crossorigin src="/assets/index-BYtByjSm.js"></script>
48
- <link rel="stylesheet" crossorigin href="/assets/index-Bn84l3Zr.css">
47
+ <script type="module" crossorigin src="/assets/index-0IC9C6Wd.js"></script>
48
+ <link rel="stylesheet" crossorigin href="/assets/index-acdiHHul.css">
49
49
  </head>
50
50
  <body>
51
51
  <div id="root"></div>
package/dist/web/prompt.md CHANGED
@@ -28,8 +28,9 @@ feedback bundle. Check `feedback.reviewScope` before editing: missing or
28
28
  `{ "mode": "all" }` means the whole turn was submitted; `{ "mode": "single" }`
29
29
  or `{ "mode": "range" }` means the human submitted feedback while viewing only
30
30
  that commit preview. Treat scoped feedback as comments on that slice, and do not
31
- infer that unreviewed commits were approved. Address every comment in file/line
32
- order, then run the narrowest relevant validation. After validation, run
31
+ infer that unreviewed commits were approved. Address general comments first,
32
+ then file/line comments in file and line order, then run the narrowest relevant
33
+ validation. After validation, run
33
34
  `gloss resolve <reviewId> --summary "<what changed>"`.
34
35
  When tracking progress comment-by-comment is useful, run
35
36
  `gloss resolve <reviewId> --comment <commentId> --summary "<what changed>"`
package/dist/web/setup/index.html CHANGED
@@ -253,7 +253,7 @@
253
253
  <pre>1. Run gloss open --json from the repo root unless the user names a base ref.
254
254
  2. Wait for the browser review to be submitted.
255
255
  3. Read feedbackPath from the JSON output.
256
- 4. Address each comment in file and line order.
256
+ 4. Address general comments first, then file comments in file and line order.
257
257
  5. Validate the fix with the narrowest relevant checks.
258
258
  6. Optionally mark individual comments handled:
259
259
  gloss resolve &lt;reviewId&gt; --comment &lt;commentId&gt; --summary "&lt;what changed&gt;"
@@ -289,6 +289,10 @@
289
289
  In the browser review, <code>Command+Enter</code> saves the active draft comment and
290
290
  <code>Command+Shift+Enter</code> submits already-saved comments.
291
291
  </p>
292
+ <p>
293
+ Gloss hides lockfiles by default in the browser review. Use browser-only filters to also
294
+ hide snapshots, generated code, and vendored code while reviewing.
295
+ </p>
292
296
  <p>Start a fresh session with the same command for follow-up diffs.</p>
293
297
  </section>
294
298
 
package/dist/web/setup.md CHANGED
@@ -4,8 +4,9 @@ You are setting yourself up to use Gloss, a local code-diff review tool for
4
4
  coding-agent loops.
5
5
 
6
6
  Gloss captures the current git diff, opens a localhost browser review UI, lets
7
- the user attach comments to changed lines and ranges, then writes structured
8
- feedback under `~/.gloss/reviews/<reviewId>/turns/<turnId>/`.
7
+ the user attach comments to changed lines/ranges or the whole review, then
8
+ writes structured feedback under
9
+ `~/.gloss/reviews/<reviewId>/turns/<turnId>/`.
9
10
 
10
11
  ## Check Installation
11
12
 
@@ -55,7 +56,7 @@ The skill pairs the CLI with the browser app:
55
56
  3. Read `feedbackPath` from the JSON output.
56
57
  4. Check `feedback.reviewScope`; scoped feedback means the human submitted while
57
58
  viewing one commit or commit range, not necessarily the whole turn.
58
- 5. Address each comment in file and line order.
59
+ 5. Address general comments first, then file comments in file and line order.
59
60
  6. Validate the fix with the narrowest relevant checks.
60
61
  7. Optionally mark individual comments handled with
61
62
  `gloss resolve <reviewId> --comment <commentId> --summary "<what changed>"`.
@@ -69,6 +70,10 @@ Browser review shortcuts:
69
70
  - `Command+Enter` saves the active draft comment.
70
71
  - `Command+Shift+Enter` submits the review with already-saved comments.
71
72
 
73
+ The browser hides lockfiles by default and can also hide snapshots, generated
74
+ code, and vendored code. Those filters affect only the browser view; submitted
75
+ feedback still refers to the full captured diff.
76
+
72
77
  ## Update Your Persistent Instructions
73
78
 
74
79
  Add Gloss guidance to the persistent instruction file this agent will actually
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "getgloss",
3
- "version": "0.12.1",
3
+ "version": "0.13.0",
4
4
  "description": "Local browser-based diff review for coding-agent loops.",
5
5
  "type": "module",
6
6
  "packageManager": "pnpm@10.33.2",
@@ -57,8 +57,8 @@
57
57
  "tsup": "8.5.1",
58
58
  "tsx": "4.22.3",
59
59
  "typescript": "5.9.3",
60
- "vite": "6.4.2",
61
- "vitest": "3.2.4"
60
+ "vite": "6.4.3",
61
+ "vitest": "3.2.6"
62
62
  },
63
63
  "keywords": [
64
64
  "diff",
package/skill/SKILL.md CHANGED
@@ -10,7 +10,7 @@ description: Open local working-tree or branch changes in Gloss for browser revi
10
10
  1. From the repo root, run `gloss open --json` unless the user names a base ref.
11
11
  2. Leave it running; it waits until browser submission. Use `--no-watch` only when the user only wants the review opened.
12
12
  3. Parse the JSON output and read `feedbackPath`.
13
- 4. Apply feedback in file/line order unless "Discussion Mode" applies.
13
+ 4. Apply general comments first, then file/line comments in file and line order unless "Discussion Mode" applies.
14
14
  5. Validate with the narrowest relevant checks.
15
15
  6. Resolve handled feedback with `gloss resolve <reviewId> --comment <commentId> --summary "<what changed>"` when useful, then `gloss resolve <reviewId> --summary "<what changed>"`.
16
16
  7. For another pass on the same work, run `gloss open --review <reviewId> --json`; use a fresh `gloss open --json` only for unrelated work.
@@ -25,7 +25,7 @@ and "propose first".
25
25
  When discussing:
26
26
 
27
27
  1. Read every comment in `feedback.json` before editing. Do not edit files yet.
28
- 2. Group comments by file. Restate each comment in one line, propose the change, and flag conflicts/out-of-scope items.
28
+ 2. Group general comments first, then file comments by file. Restate each comment in one line, propose the change, and flag conflicts/out-of-scope items.
29
29
  3. Ask which items to apply, modify, or skip, then wait for the answer.
30
30
  4. Apply only approved items, validate, then resolve as usual. Mention skipped items in the resolution summary.
31
31