@staff0rd/assist 0.1022.3 → 0.1024.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.
@@ -7,7 +7,7 @@ Parse `$ARGUMENTS`: if `--all` is present, enable **catch-up mode** (described b
7
7
 
8
8
  ## Single-week mode (default)
9
9
 
10
- Run `assist devlog next`. It prints the project `name`, the ISO `week` (e.g. `2026-W33`), its Monday–Sunday `range`, the `versions` range, and every commit in the week oldest first, each tagged with the version from `package.json` at that commit (no version is shown when the repo has none). It only ever offers completed weeks; if it reports nothing to write, stop.
10
+ Run `assist devlog next`. It prints the project `name`, the ISO `week` (e.g. `2026-W33`), its Monday–Sunday `range`, the `dates` of the first and last commits, the `versions` range, and every commit in the week oldest first, each tagged with the version from `package.json` at that commit. No versions are shown when the repo has no real version history (no tags and a version that never changes in the week). It only ever offers completed weeks; if it reports nothing to write, stop.
11
11
 
12
12
  Decide whether the week is worth an entry:
13
13
 
@@ -22,6 +22,10 @@ Never write the entry file yourself. Write the entry as JSON to a scratch file a
22
22
  {
23
23
  "week": "<week id, e.g. 2026-W33>",
24
24
  "title": "<one-line headline of the week's main themes>",
25
+ "dates": {
26
+ "first": "<first commit date in the week, YYYY-MM-DD>",
27
+ "last": "<last commit date in the week, YYYY-MM-DD>"
28
+ },
25
29
  "versions": {
26
30
  "first": "<earliest version in the week>",
27
31
  "last": "<latest version in the week>"
@@ -29,29 +33,32 @@ Never write the entry file yourself. Write the entry as JSON to a scratch file a
29
33
  "aiGenerated": "<model name, e.g. claude-opus-5>",
30
34
  "added": [
31
35
  {
32
- "text": "<one line describing something new>",
36
+ "text": "<short phrase naming something new>",
33
37
  "version": "<version of the commit(s) it came from>"
34
38
  }
35
39
  ],
36
40
  "changed": [
37
41
  {
38
- "text": "<one line describing a change to existing behaviour>",
42
+ "text": "<short phrase naming a change to existing behaviour>",
39
43
  "version": "<version>"
40
44
  }
41
45
  ],
42
- "fixed": [{ "text": "<one line describing a fix>", "version": "<version>" }],
46
+ "fixed": [
47
+ { "text": "<short phrase naming what was broken>", "version": "<version>" }
48
+ ],
43
49
  "lede": "<1-2 sentence lede summarising what the week was about>"
44
50
  }
45
51
  ```
46
52
 
47
53
  - **title**: a terse headline naming the week's 2-3 main themes (e.g. `Comment previews, Windows config writes, collapsible sidebar`), not a sentence.
48
- - **versions**: the first and last versions reported by `assist devlog next`. Omit `versions` entirely when the repo has no versions.
54
+ - **dates**: the first and last commit dates reported as `dates` by `assist devlog next`.
55
+ - **versions**: the first and last versions reported by `assist devlog next`. Omit `versions` entirely when it reports none.
49
56
  - **added / changed / fixed**: one line per user-visible change, newest version first within each list. Merge related commits into one line and drop release commits, refactors, tests and other internal-only work. Use `feat:` commits as a hint for **added** and `fix:` for **fixed**, but classify by what changed for the user. Omit a list that would be empty.
50
- - **version** on each line: the version shown against the commit(s) the line came from (the latest one when several commits are merged). Omit `version` when the repo has no versions.
51
- - Write each line as a short changelog item, not first-person prose. Wrap code symbols (commands, function names, file names, config keys) in backticks.
57
+ - **version** on each line: the version shown against the commit(s) the line came from (the latest one when several commits are merged). Omit `version` when `assist devlog next` reports no versions.
58
+ - Write each line as a short changelog phrase (at most 80 characters, which `assist devlog write` enforces), not a sentence: name the thing, drop the explanation. A fix names what was broken, e.g. "`assist backlog show` not printing comments", not "`assist backlog show` collected comments but never printed them". Wrap code symbols (commands, function names, file names, config keys) in backticks.
52
59
  - **lede**: one or two sentences, conversational, saying what the week was mostly about and why it matters.
53
60
 
54
- Read existing entries in `~/git/blog/src/content/dev/` for style if any exist.
61
+ Match the style of `~/git/blog/src/content/dev/assist/2026-w33.md`. Older entries in `~/git/blog/src/content/dev/` predate the short-phrase style, so don't copy their item length.
55
62
 
56
63
  ## Catch-up mode (`--all`)
57
64
 
@@ -3,8 +3,8 @@
3
3
  "assist@staff0rd.github.io": {
4
4
  "updates": [
5
5
  {
6
- "version": "0.1020.0",
7
- "update_link": "https://github.com/staff0rd/assist/releases/download/v0.1020.0/assist-extension.xpi"
6
+ "version": "0.1022.2",
7
+ "update_link": "https://github.com/staff0rd/assist/releases/download/v0.1022.2/assist-extension.xpi"
8
8
  }
9
9
  ]
10
10
  }