codeassembly-guidance 0.2.0 → 0.4.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.
- package/.meta/changelog.json +291 -0
- package/CHANGELOG.md +82 -0
- package/README.md +20 -121
- package/content/_partials/README.md +19 -3
- package/content/_partials/diff-audit-checklist.md +1 -0
- package/content/_partials/guidance-change-since-capture.md +9 -0
- package/content/_partials/kb-standard-tags.md +7 -0
- package/content/codeassembly-content.yaml +8 -0
- package/content/collections/recommended.md +1 -1
- package/content/guidance/README.md +1 -1
- package/content/guidance/rulebooks/cli-conventions.md +16 -2
- package/content/guidance/rulebooks/codeassembly-content-specification.md +19 -2
- package/content/guidance/rulebooks/commit-conventions.md +3 -2
- package/content/guidance/rulebooks/williamthorsen-collaboration-preferences.md +6 -2
- package/content/guidance/rulebooks/williamthorsen-writing-preferences.md +28 -1
- package/content/guidance/shared/AGENTS.md +31 -4
- package/content/scripts/check-prose.mjs +38 -38
- package/content/scripts/describe-change.mjs +69 -69
- package/content/scripts/manage-jira-ticket.mjs +73 -73
- package/content/scripts/select-lede-exemplars.mjs +53 -53
- package/content/scripts/validate-preferences.mjs +1 -1
- package/content/skills/_data/action-items.md +2 -0
- package/content/skills/_data/artifact-conventions.md +24 -3
- package/content/skills/_data/complexity-classification.md +1 -1
- package/content/skills/_data/design-priorities.md +12 -1
- package/content/skills/_data/spike-conventions.md +21 -6
- package/content/skills/_data/title-templates.md +3 -1
- package/content/skills/_partials/apply-guidance-edits.md +5 -0
- package/content/skills/_partials/cluster-feedback-events.md +21 -0
- package/content/skills/_partials/commit-title-rendering.md +1 -1
- package/content/skills/_partials/next-steps-after-plan.md +1 -1
- package/content/skills/_partials/option-format.md +2 -2
- package/content/skills/_partials/plan-template.md +4 -2
- package/content/skills/_partials/ticket-and-plan-completeness.md +1 -1
- package/content/skills/_partials/ticket-composition.md +40 -0
- package/content/skills/_partials/ticket-skeleton.md +15 -1
- package/content/skills/align-ticket-with-implementation/SKILL.md +1 -5
- package/content/skills/assess-code-health/SKILL.md +127 -0
- package/content/skills/assess-code-health/assess-code-health.mjs +77 -0
- package/content/skills/assess-usability/SKILL.md +3 -1
- package/content/skills/capture-event/SKILL.md +2 -0
- package/content/skills/capture-event/capture-event.mjs +32 -32
- package/content/skills/capture-feedback/SKILL.md +1 -1
- package/content/skills/collaborate/SKILL.md +2 -2
- package/content/skills/create-bitbucket-pr/SKILL.md +2 -1
- package/content/skills/create-commit/SKILL.md +1 -1
- package/content/skills/create-gh-pr/SKILL.md +4 -1
- package/content/skills/create-pr/SKILL.md +2 -1
- package/content/skills/create-ticket/SKILL.md +3 -7
- package/content/skills/curate-feedback/SKILL.md +102 -0
- package/content/skills/curate-feedback/curate-feedback.mjs +211 -0
- package/content/skills/derive-session-context/derive-session-context.mjs +94 -94
- package/content/skills/design-and-plan/SKILL.md +5 -9
- package/content/skills/implement-plan/SKILL.md +2 -2
- package/content/skills/index-prototypes/SKILL.md +1 -1
- package/content/skills/kb-add/SKILL.md +2 -0
- package/content/skills/kb-add/kb-add.mjs +53 -53
- package/content/skills/kb-curate/kb-curate.mjs +64 -64
- package/content/skills/kb-edit/SKILL.md +2 -0
- package/content/skills/kb-edit/kb-edit.mjs +59 -59
- package/content/skills/kb-retrieve/kb-retrieve.mjs +75 -75
- package/content/skills/kb-retrieve-events/SKILL.md +19 -10
- package/content/skills/kb-retrieve-events/kb-retrieve-events.mjs +75 -75
- package/content/skills/kb-update-events/SKILL.md +9 -6
- package/content/skills/kb-update-events/kb-update-events.mjs +86 -85
- package/content/skills/lesson-clusters/lesson-clusters.mjs +209 -0
- package/content/skills/migrate-feedback-memories/feedback-memories.mjs +75 -75
- package/content/skills/plan/SKILL.md +1 -1
- package/content/skills/refine-guidance/SKILL.md +97 -0
- package/content/skills/review-branch/SKILL.md +350 -1
- package/content/skills/revise-prose/revise-prose.mjs +103 -103
- package/content/skills/save-artifact/SKILL.md +1 -1
- package/content/skills/streamline-guidance/SKILL.md +10 -15
- package/content/skills/streamline-guidance/streamline-guidance.mjs +74 -74
- package/content/skills/summarize-change/SKILL.md +1 -1
- package/content/skills/testing-conventions/SKILL.md +7 -1
- package/content/skills/triage-feedback/SKILL.md +135 -0
- package/content/skills/triage-feedback/triage-feedback.mjs +70 -0
- package/content/skills/triage-spike-findings/SKILL.md +6 -6
- package/content/skills/triage-spike-findings/triage-spike-findings.mjs +30 -28
- package/content/skills/update-project-guidance/SKILL.md +10 -10
- package/content/subagents/code-health-assessor.md +98 -0
- package/content/subagents/feedback-coverage-judge.md +95 -0
- package/content/subagents/feedback-triage-challenger.md +86 -0
- package/content/subagents/lesson-clusterer.md +68 -0
- package/package.json +13 -13
- package/schemas/preferences.v1.json +22 -6
- package/schemas/work-types.v1.json +1 -1
- package/content/_partials/code-descriptions.md +0 -4
- package/content/_partials/code-style.md +0 -7
- package/content/_partials/live-repo-writes.md +0 -13
- package/content/_partials/reduced-object-relative.md +0 -28
- package/content/_partials/test-structure-audit-checklist.md +0 -7
- package/content/skills/_partials/acceptance-criteria-scaffold.md +0 -15
- package/content/skills/_partials/next-steps-after-review.md +0 -350
- package/content/skills/_partials/ticket-concision.md +0 -18
- package/content/skills/_partials/ticket-placement.md +0 -14
- package/content/skills/_partials/ticket-skeleton-tiers.md +0 -6
package/.meta/changelog.json
CHANGED
|
@@ -1,4 +1,295 @@
|
|
|
1
1
|
[
|
|
2
|
+
{
|
|
3
|
+
"version": "0.4.0",
|
|
4
|
+
"date": "2026-11-02",
|
|
5
|
+
"sections": [
|
|
6
|
+
{
|
|
7
|
+
"title": "🎉 Features",
|
|
8
|
+
"audience": "all",
|
|
9
|
+
"items": [
|
|
10
|
+
{
|
|
11
|
+
"description": "Adds the `curate-feedback` skill, which has `feedback-coverage-judge` subagents sort each open feedback event into covered, duplicate, obsolete, or kept against guidance pinned at a commit, and then, after approval or under `--apply`, marks every event that is not kept through `kb-update-events` and records the run in a `feedback-curation` artifact. (#2231)",
|
|
12
|
+
"hash": "6bb5907a3426bb91a6f1a4a340b3a4180576a503",
|
|
13
|
+
"entry": 1
|
|
14
|
+
},
|
|
15
|
+
{
|
|
16
|
+
"description": "Adds each covered entry's quote to the `feedback-curation` artifact's events table and to the approval table that `curate-feedback --list` presents, so that the developer can check every covered verdict against its stating sentence before approving the marks. (#2236)",
|
|
17
|
+
"hash": "73c4bd7e28cccf9b4875a18c491993ac371869df",
|
|
18
|
+
"entry": 2
|
|
19
|
+
}
|
|
20
|
+
]
|
|
21
|
+
},
|
|
22
|
+
{
|
|
23
|
+
"title": "🪦 Removed",
|
|
24
|
+
"audience": "all",
|
|
25
|
+
"items": [
|
|
26
|
+
{
|
|
27
|
+
"description": "Remove the factory and the demos (#2234)",
|
|
28
|
+
"body": "Removes the dormant factory visualization package and the catwalk demos, together with the docs, repo-local skills, dependencies, and configuration that only they used. Adds to `docs/repository-split.md` the command that finds the last commit containing the factory, which is the commit from which a revival restores it.",
|
|
29
|
+
"hash": "a2715300691038525090dd8299b4c6602fbba607"
|
|
30
|
+
}
|
|
31
|
+
]
|
|
32
|
+
},
|
|
33
|
+
{
|
|
34
|
+
"title": "🐛 Bug fixes",
|
|
35
|
+
"audience": "all",
|
|
36
|
+
"items": [
|
|
37
|
+
{
|
|
38
|
+
"description": "Fixes the issue that the `feedback-coverage-judge` subagent of `curate-feedback` marked a feedback event `obsolete` when the change that removed the event's target had renamed or moved it, or had named a replacement for it. (#2233)",
|
|
39
|
+
"hash": "628e9f86e2b47f4b63922468157f31e4da5c2155",
|
|
40
|
+
"entry": 1
|
|
41
|
+
},
|
|
42
|
+
{
|
|
43
|
+
"description": "Fixes the issue that `curate-feedback validate` accepted a `covered` entry after checking only that the cited guidance file existed, by requiring a verbatim `quote` of the stating sentence and rejecting the entry when the file at the pin does not contain it, ignoring differences in whitespace and in `*`, `_`, and backtick markers. (#2236)",
|
|
44
|
+
"hash": "73c4bd7e28cccf9b4875a18c491993ac371869df",
|
|
45
|
+
"entry": 1
|
|
46
|
+
},
|
|
47
|
+
{
|
|
48
|
+
"description": "Fixes the issue that `triage-feedback` ranked a feedback cluster by its events even when all of them predated a change to the guidance that governs its lesson, and directs the skill and its `feedback-triage-challenger` subagent to check that guidance's commit history and set such a cluster to `low` unless evidence shows the failure recurring under the changed guidance. (#2243)",
|
|
49
|
+
"hash": "4d16db28a5e06835ecee87bd6d07c758d9ce00b4",
|
|
50
|
+
"entry": 1
|
|
51
|
+
},
|
|
52
|
+
{
|
|
53
|
+
"description": "Fixes the issue that `triage-feedback` and `triage-spike-findings` accepted a defense against the challenger that rested on grounds other than the evidence named by the challenger's argument. (#2243)",
|
|
54
|
+
"hash": "4d16db28a5e06835ecee87bd6d07c758d9ce00b4",
|
|
55
|
+
"entry": 2
|
|
56
|
+
},
|
|
57
|
+
{
|
|
58
|
+
"description": "Remove the unshipped `source` export condition from the published packages (#2244)",
|
|
59
|
+
"body": "Removes the `source` export condition from `codeassembly`, `@williamthorsen/kb`, and `codeassembly-run-core`, because it pointed at TypeScript files that their tarballs don't contain, so that a consumer that enables the condition resolves the shipped `dist/` output instead of failing.",
|
|
60
|
+
"hash": "1e1dfc9f376b90956f1c769e0d439a142d43a84b"
|
|
61
|
+
}
|
|
62
|
+
]
|
|
63
|
+
}
|
|
64
|
+
]
|
|
65
|
+
},
|
|
66
|
+
{
|
|
67
|
+
"version": "0.3.0",
|
|
68
|
+
"date": "2026-11-01",
|
|
69
|
+
"sections": [
|
|
70
|
+
{
|
|
71
|
+
"title": "🎉 Features",
|
|
72
|
+
"audience": "all",
|
|
73
|
+
"items": [
|
|
74
|
+
{
|
|
75
|
+
"description": "Adds a \"Who applies the change\" section to `design-priorities.md`, which ranks a design that the agent applies and verifies itself above one that needs a person to run a step on each machine, orders three ways to shape a step that stays (reach the machine through its existing access, route the step through its existing provisioning, or leave one self-checking script per machine), and is cited by `design-and-plan` and `plan` when they rank approaches. (#2175)",
|
|
76
|
+
"hash": "ce936e76d019c1eeba400a8a191e05600a4f0c3b",
|
|
77
|
+
"entry": 1
|
|
78
|
+
},
|
|
79
|
+
{
|
|
80
|
+
"description": "Changes the plan template's `**Residue:**` rule so that a step that a person must run on each machine is written as one script per machine that checks its own result, and so that a record of the work, such as a log entry or a ticket comment, is never residue, which `implement-plan` also states. (#2175)",
|
|
81
|
+
"hash": "ce936e76d019c1eeba400a8a191e05600a4f0c3b",
|
|
82
|
+
"entry": 2
|
|
83
|
+
},
|
|
84
|
+
{
|
|
85
|
+
"description": "Adds a rule to the `williamthorsen-collaboration-preferences` rulebook and the `collaborate` skill that directs the agent to answer a question from the developer rather than hand over a procedure to run, to run any check that the answer needs, and to count the commands that it hands over across the session. (#2175)",
|
|
86
|
+
"hash": "ce936e76d019c1eeba400a8a191e05600a4f0c3b",
|
|
87
|
+
"entry": 3
|
|
88
|
+
},
|
|
89
|
+
{
|
|
90
|
+
"description": "Adds a rule to the `williamthorsen-collaboration-preferences` rulebook that directs the agent, once the developer signals overload, to stop adding asks and to end each turn without an action-items block until the developer asks for something, and points `action-items.md` and the `collaborate` skill to it. (#2175)",
|
|
91
|
+
"hash": "ce936e76d019c1eeba400a8a191e05600a4f0c3b",
|
|
92
|
+
"entry": 4
|
|
93
|
+
},
|
|
94
|
+
{
|
|
95
|
+
"description": "Adds a \"Check results\" section to the `cli-conventions` rulebook, which requires a `check` or `verify` mode, a health probe, or a pre-flight to state on each item's line what it checked and the state that it found, to show a failure's evidence (a diff or the actual state) without `--verbose`, and to probe end to end the function that a configuration-only check serves. (#2178)",
|
|
96
|
+
"hash": "50524b6f50c43baf9a9831d84c6db40e3039e139",
|
|
97
|
+
"entry": 1
|
|
98
|
+
},
|
|
99
|
+
{
|
|
100
|
+
"description": "Adds a \"Documentation placement\" section to the shared `AGENTS.md` guidance, which directs an agent that writes a guidance or documentation file to point to the config, code, README section, or rulebook that defines a fact and to add only what that source does not state. (#2181)",
|
|
101
|
+
"hash": "ca4381616aa1f033c4ff84dd0ceba58b39dbf6eb",
|
|
102
|
+
"entry": 1
|
|
103
|
+
},
|
|
104
|
+
{
|
|
105
|
+
"description": "Directs the plan template used by `plan` and `design-and-plan` to name, in the key decisions of each task that writes guidance or documentation, the source that defines each documented fact. (#2181)",
|
|
106
|
+
"hash": "ca4381616aa1f033c4ff84dd0ceba58b39dbf6eb",
|
|
107
|
+
"entry": 2
|
|
108
|
+
},
|
|
109
|
+
{
|
|
110
|
+
"description": "Adds a placement item to the diff audit run by `implement-plan`, `respond-to-review`, and `revise-comments`, which checks that each guidance or documentation hunk points to a fact's source rather than copying the fact. (#2181)",
|
|
111
|
+
"hash": "ca4381616aa1f033c4ff84dd0ceba58b39dbf6eb",
|
|
112
|
+
"entry": 3
|
|
113
|
+
},
|
|
114
|
+
{
|
|
115
|
+
"description": "Extends the duplication check in `update-project-guidance` from the global guidance file to rulebooks loaded into the session and to repository files, so that the skill omits what loaded guidance already states and points to a repository file that defines a fact. (#2181)",
|
|
116
|
+
"hash": "ca4381616aa1f033c4ff84dd0ceba58b39dbf6eb",
|
|
117
|
+
"entry": 4
|
|
118
|
+
},
|
|
119
|
+
{
|
|
120
|
+
"description": "Changes the marker that the `williamthorsen-collaboration-preferences` rulebook and the plan and option-format templates prescribe for a decision awaiting the developer's checkpoint from ⏳ to 🔲, an unchecked box that reads as an item still to approve rather than as work in progress. (#2185)",
|
|
121
|
+
"hash": "9e34f69741792807f5a2e96fa14e0859afe0fea6",
|
|
122
|
+
"entry": 1
|
|
123
|
+
},
|
|
124
|
+
{
|
|
125
|
+
"description": "Adds a `defects` field to the JSON output of `consolidate-entries`, which lists each entry whose breaking marker violates its type's policy or whose type the taxonomy does not declare, naming the entry by its 0-based index with the same `policy-violation` and `undeclared-type` kinds that `resolve-merge` reports. (#2186)",
|
|
126
|
+
"hash": "619b29d634352c19777eb04639d328f52ad7c1e3",
|
|
127
|
+
"entry": 1
|
|
128
|
+
},
|
|
129
|
+
{
|
|
130
|
+
"description": "Directs `summarize-change` to report each entry defect that `consolidate-entries` returns, naming the entry by its `text`, and to continue without changing anything. (#2186)",
|
|
131
|
+
"hash": "619b29d634352c19777eb04639d328f52ad7c1e3",
|
|
132
|
+
"entry": 2
|
|
133
|
+
},
|
|
134
|
+
{
|
|
135
|
+
"description": "Adds the closing post to `spike-conventions.md`, a ticket comment that contains the answers to the ticket's questions, the recommendations on its decisions, and links to the findings artifact and, when the spike published one, to its page, and names the post in the deliverables of the spike ticket and plan templates. (#2196)",
|
|
136
|
+
"hash": "d3ecb9b8b52ee6e8fc358d596a7c8caf3911769a",
|
|
137
|
+
"entry": 1
|
|
138
|
+
},
|
|
139
|
+
{
|
|
140
|
+
"description": "Adds an offer of the closing post to the action-items block of the `assess-usability` report step, and replaces the skill's statement that it writes nothing remote with one that names this post, made on consent, as its one remote write. (#2196)",
|
|
141
|
+
"hash": "d3ecb9b8b52ee6e8fc358d596a7c8caf3911769a",
|
|
142
|
+
"entry": 2
|
|
143
|
+
},
|
|
144
|
+
{
|
|
145
|
+
"description": "Extends the 🔬 Investigate option for a spike plan, shown in the next-steps menu of `design-and-plan`, `plan`, `refine-plan`, and `save-plan`, to end the run with the plan's `## Deliverable`, which includes the offer of the closing post. (#2196)",
|
|
146
|
+
"hash": "d3ecb9b8b52ee6e8fc358d596a7c8caf3911769a",
|
|
147
|
+
"entry": 3
|
|
148
|
+
},
|
|
149
|
+
{
|
|
150
|
+
"description": "Adds a rule to `artifact-conventions.md` that a conclusion needed by a reader of the ticket is posted on the ticket, while the artifact keeps the evidence. (#2196)",
|
|
151
|
+
"hash": "d3ecb9b8b52ee6e8fc358d596a7c8caf3911769a",
|
|
152
|
+
"entry": 4
|
|
153
|
+
},
|
|
154
|
+
{
|
|
155
|
+
"description": "Adds the `pr.initial_state` preference (`draft` or `ready`, default `draft`), which `create-pr` reads from the project or global preferences file to open a pull request as a draft or ready for review, and makes `pr.title_format` optional so that a `pr` section can set only the state. (#2198)",
|
|
156
|
+
"hash": "bd2088a0b09c9767138ab1226ba684a666f3a9ca",
|
|
157
|
+
"entry": 1
|
|
158
|
+
},
|
|
159
|
+
{
|
|
160
|
+
"description": "Adds the `--add-tag` operation to `kb-update-events`, which appends the given tags, canonicalized through the store's alias map, to each named event's tags and leaves an event that already has all of them untouched, unlike `--retag`, which replaces the whole set. (#2208)",
|
|
161
|
+
"hash": "420d2b3f78bc56293cef181579b94fafcfed5197",
|
|
162
|
+
"entry": 1
|
|
163
|
+
},
|
|
164
|
+
{
|
|
165
|
+
"description": "Adds `--help` to the `kb-update-events` helper, which prints usage describing every operation and exits without updating any event. (#2208)",
|
|
166
|
+
"hash": "420d2b3f78bc56293cef181579b94fafcfed5197",
|
|
167
|
+
"entry": 2
|
|
168
|
+
},
|
|
169
|
+
{
|
|
170
|
+
"description": "Adds an `--exclude-tag` flag to `kb-retrieve-events` that takes a comma-separated list of tags, matched in canonical or alias form, and drops every event that has any of them; a repeated flag adds to the list. (#2209)",
|
|
171
|
+
"hash": "0c30f1befb520f3698d7016e092e3680b479e4e3",
|
|
172
|
+
"entry": 1
|
|
173
|
+
},
|
|
174
|
+
{
|
|
175
|
+
"description": "Adds a \"Standard tags\" section, generated from `STANDARD_TAGS`, to the skills that write or filter knowledge-base tags, such as `capture-event` and `kb-update-events`, which directs the agent to tag a record's disposition by a standard name rather than a variant spelling. (#2212)",
|
|
176
|
+
"hash": "2c1413e55ca6061c6133c6ed74ddcae6809923e6",
|
|
177
|
+
"entry": 2
|
|
178
|
+
},
|
|
179
|
+
{
|
|
180
|
+
"description": "Adds an optional `evidence` field (a stable `key` and the `paths` that it covers) to each item of the `triage-spike-findings` record and an optional `commit` field to the record, which `validate` requires once any item has evidence, and adds to the end of the dispositions comment a hidden, versioned JSON block that the exported `parseEvidenceBlock` function reads back. (#2213)",
|
|
181
|
+
"hash": "03cb1f7b2538d8bf0c9c43824a68c4b1f4ae6d7a",
|
|
182
|
+
"entry": 1
|
|
183
|
+
},
|
|
184
|
+
{
|
|
185
|
+
"description": "Has the `triage-spike-findings` skill copy each item's evidence key and paths from the findings into the inventory and the record, and set the record's `commit` to the HEAD at which the developer approved the dispositions. (#2213)",
|
|
186
|
+
"hash": "03cb1f7b2538d8bf0c9c43824a68c4b1f4ae6d7a",
|
|
187
|
+
"entry": 2
|
|
188
|
+
},
|
|
189
|
+
{
|
|
190
|
+
"description": "Adds the `assess-code-health` skill, which measures git hotspots and test coverage for one package or subtree, dispatches five `code-health-assessor` subagents (conventions, structure, extraction, error handling, and tests), and ranks the proposals whose cited evidence resolves against the tree in a `code-health-findings` artifact that `triage-spike-findings` now accepts as input. (#2216)",
|
|
191
|
+
"hash": "45388be8981d097f6851d70c99212c27a4497b87",
|
|
192
|
+
"entry": 1
|
|
193
|
+
},
|
|
194
|
+
{
|
|
195
|
+
"description": "Adds the `triage-feedback` skill, which groups the open events of a feedback store by lesson, shows the top `--limit` clusters with each one's recurrence, impact, and latest capture, has a subagent without session context challenge every priority, and after one approval files a ticket, comments on an open issue that already covers the lesson, defers the cluster, or changes its impact rating. (#2217)",
|
|
196
|
+
"hash": "fe3c3febce8753d879729b34a2cbce26d245cb06",
|
|
197
|
+
"entry": 1
|
|
198
|
+
},
|
|
199
|
+
{
|
|
200
|
+
"description": "Adds the `triage_feedback.defer_days` preference, which sets the number of days for which `triage-feedback` leaves a deferred cluster out of a triage unless the cluster gains a new event, 30 by default. (#2217)",
|
|
201
|
+
"hash": "fe3c3febce8753d879729b34a2cbce26d245cb06",
|
|
202
|
+
"entry": 2
|
|
203
|
+
},
|
|
204
|
+
{
|
|
205
|
+
"description": "Adds the `refine-guidance` skill, which finds the rule that already states a lesson or places a new artifact, drafts the edits for approval, opens a pull request, and marks the lesson's feedback events as addressed by it. (#2227)",
|
|
206
|
+
"hash": "255356fab78972974cd632ee3f7b373e699382e0",
|
|
207
|
+
"entry": 1
|
|
208
|
+
},
|
|
209
|
+
{
|
|
210
|
+
"description": "Adds a \"Choosing a kind\" section to the `codeassembly-content-specification` rulebook, which states the kind of artifact and the content root in which a lesson belongs, and when to change an existing rule rather than add a parallel one. (#2227)",
|
|
211
|
+
"hash": "255356fab78972974cd632ee3f7b373e699382e0",
|
|
212
|
+
"entry": 2
|
|
213
|
+
}
|
|
214
|
+
]
|
|
215
|
+
},
|
|
216
|
+
{
|
|
217
|
+
"title": "🐛 Bug fixes",
|
|
218
|
+
"audience": "all",
|
|
219
|
+
"items": [
|
|
220
|
+
{
|
|
221
|
+
"description": "Fixes the issue that the commit guidance did not say which source sets a commit title's format, by stating in `commit-conventions` that `commit.title_format` alone sets it and by directing agents in `create-commit` and the shared `AGENTS.md` not to change a rendered title to match other commits or comment on whether it contains a ticket reference. (#2172)",
|
|
222
|
+
"hash": "31c4f2f65fe8bc6b739c8e4ed5a355f8fa961e6f",
|
|
223
|
+
"entry": 1
|
|
224
|
+
},
|
|
225
|
+
{
|
|
226
|
+
"description": "Fixes the issue that `create-commit` and `condense-branch` did not give agents a title to use when `commit.title_format` is empty or unset and the renderer printed an empty title; both now fall back to the bare title. (#2172)",
|
|
227
|
+
"hash": "31c4f2f65fe8bc6b739c8e4ed5a355f8fa961e6f",
|
|
228
|
+
"entry": 2
|
|
229
|
+
},
|
|
230
|
+
{
|
|
231
|
+
"description": "Fixes the issue that `index-prototypes` had the agent ask the developer to run `chrome-debug`, which is no longer installed, on a refused Playwright connection, rather than run `thor-chrome` itself and ask only when `thor-chrome` refuses the launch with `session-unavailable`. (#2192)",
|
|
232
|
+
"hash": "648c64452d4fb11077e30427c3b18a1eb9e001f2",
|
|
233
|
+
"entry": 1
|
|
234
|
+
},
|
|
235
|
+
{
|
|
236
|
+
"description": "Fixes the issue that a section in the project `.agents/preferences.yaml` hid every global key of the same section, such as a `ticket.base_url` set only in `~/.agents/preferences.yaml`, which made `derive-session-context` report `ticket_base_url: null` and leave a Jira ticket ID without a URL. (#2199)",
|
|
237
|
+
"hash": "01f8ae785329378a0efa269b8d2561c265027291",
|
|
238
|
+
"entry": 1
|
|
239
|
+
},
|
|
240
|
+
{
|
|
241
|
+
"description": "Fixes the issue that the `--tag` filter of `kb-retrieve` and `kb-retrieve-events` compared tags literally and missed a note tagged with an alias of the requested tag, although both skills document a match on the canonical or alias form. (#2209)",
|
|
242
|
+
"hash": "0c30f1befb520f3698d7016e092e3680b479e4e3",
|
|
243
|
+
"entry": 2
|
|
244
|
+
}
|
|
245
|
+
]
|
|
246
|
+
},
|
|
247
|
+
{
|
|
248
|
+
"title": "🏗️ Internal features",
|
|
249
|
+
"audience": "dev",
|
|
250
|
+
"items": [
|
|
251
|
+
{
|
|
252
|
+
"description": "Adds a section to `_partials/README.md` that states when content becomes a partial and when partials merge, and adds `partial-consumers.unit.test.ts`, which fails when fewer than two files include a partial or when partials with the same includers are neither merged nor listed in that section. (#2183)",
|
|
253
|
+
"hash": "c6375bb111421af6e711323427be379169710dca",
|
|
254
|
+
"entry": 2
|
|
255
|
+
}
|
|
256
|
+
]
|
|
257
|
+
},
|
|
258
|
+
{
|
|
259
|
+
"title": "♻️ Refactoring",
|
|
260
|
+
"audience": "dev",
|
|
261
|
+
"items": [
|
|
262
|
+
{
|
|
263
|
+
"description": "Inlines the partials that only one file includes into that file, and merges the five ticket partials into `ticket-skeleton` and `ticket-composition`. (#2183)",
|
|
264
|
+
"hash": "c6375bb111421af6e711323427be379169710dca",
|
|
265
|
+
"entry": 1
|
|
266
|
+
}
|
|
267
|
+
]
|
|
268
|
+
},
|
|
269
|
+
{
|
|
270
|
+
"title": "🧪 Tests",
|
|
271
|
+
"audience": "dev",
|
|
272
|
+
"items": [
|
|
273
|
+
{
|
|
274
|
+
"description": "Replaces six per-doctrine reach test files with `doctrine-reach.unit.test.ts`, which runs the same checks for each entry in the `DOCTRINE_REACH` table in `test-utils/doctrine-reach.ts`. (#2183)",
|
|
275
|
+
"hash": "c6375bb111421af6e711323427be379169710dca",
|
|
276
|
+
"entry": 3
|
|
277
|
+
}
|
|
278
|
+
]
|
|
279
|
+
},
|
|
280
|
+
{
|
|
281
|
+
"title": "📦 Dependencies",
|
|
282
|
+
"audience": "dev",
|
|
283
|
+
"items": [
|
|
284
|
+
{
|
|
285
|
+
"description": "Move the test runner to Vitest 5 (#2193)",
|
|
286
|
+
"body": "Upgrades `vitest` and `@vitest/coverage-v8` from v4 to 5.0.5, and lowers from 7 days to pnpm's 24-hour `minimumReleaseAge` the age at which `nmr upgrade` proposes a third-party release.",
|
|
287
|
+
"hash": "15fb4f9908aaf7da9e1552e6a2a9cd626ee3daa2"
|
|
288
|
+
}
|
|
289
|
+
]
|
|
290
|
+
}
|
|
291
|
+
]
|
|
292
|
+
},
|
|
2
293
|
{
|
|
3
294
|
"version": "0.2.0",
|
|
4
295
|
"date": "2026-10-23",
|
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,88 @@
|
|
|
2
2
|
|
|
3
3
|
All notable changes to this project will be documented in this file.
|
|
4
4
|
|
|
5
|
+
## 0.4.0 — 2026-11-02
|
|
6
|
+
|
|
7
|
+
### 🎉 Features
|
|
8
|
+
|
|
9
|
+
- Adds the `curate-feedback` skill, which has `feedback-coverage-judge` subagents sort each open feedback event into covered, duplicate, obsolete, or kept against guidance pinned at a commit, and then, after approval or under `--apply`, marks every event that is not kept through `kb-update-events` and records the run in a `feedback-curation` artifact. (#2231)
|
|
10
|
+
- Adds each covered entry's quote to the `feedback-curation` artifact's events table and to the approval table that `curate-feedback --list` presents, so that the developer can check every covered verdict against its stating sentence before approving the marks. (#2236)
|
|
11
|
+
|
|
12
|
+
### 🪦 Removed
|
|
13
|
+
|
|
14
|
+
- Remove the factory and the demos (#2234)
|
|
15
|
+
|
|
16
|
+
Removes the dormant factory visualization package and the catwalk demos, together with the docs, repo-local skills, dependencies, and configuration that only they used. Adds to `docs/repository-split.md` the command that finds the last commit containing the factory, which is the commit from which a revival restores it.
|
|
17
|
+
|
|
18
|
+
### 🐛 Bug fixes
|
|
19
|
+
|
|
20
|
+
- Fixes the issue that the `feedback-coverage-judge` subagent of `curate-feedback` marked a feedback event `obsolete` when the change that removed the event's target had renamed or moved it, or had named a replacement for it. (#2233)
|
|
21
|
+
- Fixes the issue that `curate-feedback validate` accepted a `covered` entry after checking only that the cited guidance file existed, by requiring a verbatim `quote` of the stating sentence and rejecting the entry when the file at the pin does not contain it, ignoring differences in whitespace and in `*`, `_`, and backtick markers. (#2236)
|
|
22
|
+
- Fixes the issue that `triage-feedback` ranked a feedback cluster by its events even when all of them predated a change to the guidance that governs its lesson, and directs the skill and its `feedback-triage-challenger` subagent to check that guidance's commit history and set such a cluster to `low` unless evidence shows the failure recurring under the changed guidance. (#2243)
|
|
23
|
+
- Fixes the issue that `triage-feedback` and `triage-spike-findings` accepted a defense against the challenger that rested on grounds other than the evidence named by the challenger's argument. (#2243)
|
|
24
|
+
- Remove the unshipped `source` export condition from the published packages (#2244)
|
|
25
|
+
|
|
26
|
+
Removes the `source` export condition from `codeassembly`, `@williamthorsen/kb`, and `codeassembly-run-core`, because it pointed at TypeScript files that their tarballs don't contain, so that a consumer that enables the condition resolves the shipped `dist/` output instead of failing.
|
|
27
|
+
|
|
28
|
+
## 0.3.0 — 2026-11-01
|
|
29
|
+
|
|
30
|
+
### 🎉 Features
|
|
31
|
+
|
|
32
|
+
- Adds a "Who applies the change" section to `design-priorities.md`, which ranks a design that the agent applies and verifies itself above one that needs a person to run a step on each machine, orders three ways to shape a step that stays (reach the machine through its existing access, route the step through its existing provisioning, or leave one self-checking script per machine), and is cited by `design-and-plan` and `plan` when they rank approaches. (#2175)
|
|
33
|
+
- Changes the plan template's `**Residue:**` rule so that a step that a person must run on each machine is written as one script per machine that checks its own result, and so that a record of the work, such as a log entry or a ticket comment, is never residue, which `implement-plan` also states. (#2175)
|
|
34
|
+
- Adds a rule to the `williamthorsen-collaboration-preferences` rulebook and the `collaborate` skill that directs the agent to answer a question from the developer rather than hand over a procedure to run, to run any check that the answer needs, and to count the commands that it hands over across the session. (#2175)
|
|
35
|
+
- Adds a rule to the `williamthorsen-collaboration-preferences` rulebook that directs the agent, once the developer signals overload, to stop adding asks and to end each turn without an action-items block until the developer asks for something, and points `action-items.md` and the `collaborate` skill to it. (#2175)
|
|
36
|
+
- Adds a "Check results" section to the `cli-conventions` rulebook, which requires a `check` or `verify` mode, a health probe, or a pre-flight to state on each item's line what it checked and the state that it found, to show a failure's evidence (a diff or the actual state) without `--verbose`, and to probe end to end the function that a configuration-only check serves. (#2178)
|
|
37
|
+
- Adds a "Documentation placement" section to the shared `AGENTS.md` guidance, which directs an agent that writes a guidance or documentation file to point to the config, code, README section, or rulebook that defines a fact and to add only what that source does not state. (#2181)
|
|
38
|
+
- Directs the plan template used by `plan` and `design-and-plan` to name, in the key decisions of each task that writes guidance or documentation, the source that defines each documented fact. (#2181)
|
|
39
|
+
- Adds a placement item to the diff audit run by `implement-plan`, `respond-to-review`, and `revise-comments`, which checks that each guidance or documentation hunk points to a fact's source rather than copying the fact. (#2181)
|
|
40
|
+
- Extends the duplication check in `update-project-guidance` from the global guidance file to rulebooks loaded into the session and to repository files, so that the skill omits what loaded guidance already states and points to a repository file that defines a fact. (#2181)
|
|
41
|
+
- Changes the marker that the `williamthorsen-collaboration-preferences` rulebook and the plan and option-format templates prescribe for a decision awaiting the developer's checkpoint from ⏳ to 🔲, an unchecked box that reads as an item still to approve rather than as work in progress. (#2185)
|
|
42
|
+
- Adds a `defects` field to the JSON output of `consolidate-entries`, which lists each entry whose breaking marker violates its type's policy or whose type the taxonomy does not declare, naming the entry by its 0-based index with the same `policy-violation` and `undeclared-type` kinds that `resolve-merge` reports. (#2186)
|
|
43
|
+
- Directs `summarize-change` to report each entry defect that `consolidate-entries` returns, naming the entry by its `text`, and to continue without changing anything. (#2186)
|
|
44
|
+
- Adds the closing post to `spike-conventions.md`, a ticket comment that contains the answers to the ticket's questions, the recommendations on its decisions, and links to the findings artifact and, when the spike published one, to its page, and names the post in the deliverables of the spike ticket and plan templates. (#2196)
|
|
45
|
+
- Adds an offer of the closing post to the action-items block of the `assess-usability` report step, and replaces the skill's statement that it writes nothing remote with one that names this post, made on consent, as its one remote write. (#2196)
|
|
46
|
+
- Extends the 🔬 Investigate option for a spike plan, shown in the next-steps menu of `design-and-plan`, `plan`, `refine-plan`, and `save-plan`, to end the run with the plan's `## Deliverable`, which includes the offer of the closing post. (#2196)
|
|
47
|
+
- Adds a rule to `artifact-conventions.md` that a conclusion needed by a reader of the ticket is posted on the ticket, while the artifact keeps the evidence. (#2196)
|
|
48
|
+
- Adds the `pr.initial_state` preference (`draft` or `ready`, default `draft`), which `create-pr` reads from the project or global preferences file to open a pull request as a draft or ready for review, and makes `pr.title_format` optional so that a `pr` section can set only the state. (#2198)
|
|
49
|
+
- Adds the `--add-tag` operation to `kb-update-events`, which appends the given tags, canonicalized through the store's alias map, to each named event's tags and leaves an event that already has all of them untouched, unlike `--retag`, which replaces the whole set. (#2208)
|
|
50
|
+
- Adds `--help` to the `kb-update-events` helper, which prints usage describing every operation and exits without updating any event. (#2208)
|
|
51
|
+
- Adds an `--exclude-tag` flag to `kb-retrieve-events` that takes a comma-separated list of tags, matched in canonical or alias form, and drops every event that has any of them; a repeated flag adds to the list. (#2209)
|
|
52
|
+
- Adds a "Standard tags" section, generated from `STANDARD_TAGS`, to the skills that write or filter knowledge-base tags, such as `capture-event` and `kb-update-events`, which directs the agent to tag a record's disposition by a standard name rather than a variant spelling. (#2212)
|
|
53
|
+
- Adds an optional `evidence` field (a stable `key` and the `paths` that it covers) to each item of the `triage-spike-findings` record and an optional `commit` field to the record, which `validate` requires once any item has evidence, and adds to the end of the dispositions comment a hidden, versioned JSON block that the exported `parseEvidenceBlock` function reads back. (#2213)
|
|
54
|
+
- Has the `triage-spike-findings` skill copy each item's evidence key and paths from the findings into the inventory and the record, and set the record's `commit` to the HEAD at which the developer approved the dispositions. (#2213)
|
|
55
|
+
- Adds the `assess-code-health` skill, which measures git hotspots and test coverage for one package or subtree, dispatches five `code-health-assessor` subagents (conventions, structure, extraction, error handling, and tests), and ranks the proposals whose cited evidence resolves against the tree in a `code-health-findings` artifact that `triage-spike-findings` now accepts as input. (#2216)
|
|
56
|
+
- Adds the `triage-feedback` skill, which groups the open events of a feedback store by lesson, shows the top `--limit` clusters with each one's recurrence, impact, and latest capture, has a subagent without session context challenge every priority, and after one approval files a ticket, comments on an open issue that already covers the lesson, defers the cluster, or changes its impact rating. (#2217)
|
|
57
|
+
- Adds the `triage_feedback.defer_days` preference, which sets the number of days for which `triage-feedback` leaves a deferred cluster out of a triage unless the cluster gains a new event, 30 by default. (#2217)
|
|
58
|
+
- Adds the `refine-guidance` skill, which finds the rule that already states a lesson or places a new artifact, drafts the edits for approval, opens a pull request, and marks the lesson's feedback events as addressed by it. (#2227)
|
|
59
|
+
- Adds a "Choosing a kind" section to the `codeassembly-content-specification` rulebook, which states the kind of artifact and the content root in which a lesson belongs, and when to change an existing rule rather than add a parallel one. (#2227)
|
|
60
|
+
|
|
61
|
+
### 🐛 Bug fixes
|
|
62
|
+
|
|
63
|
+
- Fixes the issue that the commit guidance did not say which source sets a commit title's format, by stating in `commit-conventions` that `commit.title_format` alone sets it and by directing agents in `create-commit` and the shared `AGENTS.md` not to change a rendered title to match other commits or comment on whether it contains a ticket reference. (#2172)
|
|
64
|
+
- Fixes the issue that `create-commit` and `condense-branch` did not give agents a title to use when `commit.title_format` is empty or unset and the renderer printed an empty title; both now fall back to the bare title. (#2172)
|
|
65
|
+
- Fixes the issue that `index-prototypes` had the agent ask the developer to run `chrome-debug`, which is no longer installed, on a refused Playwright connection, rather than run `thor-chrome` itself and ask only when `thor-chrome` refuses the launch with `session-unavailable`. (#2192)
|
|
66
|
+
- Fixes the issue that a section in the project `.agents/preferences.yaml` hid every global key of the same section, such as a `ticket.base_url` set only in `~/.agents/preferences.yaml`, which made `derive-session-context` report `ticket_base_url: null` and leave a Jira ticket ID without a URL. (#2199)
|
|
67
|
+
- Fixes the issue that the `--tag` filter of `kb-retrieve` and `kb-retrieve-events` compared tags literally and missed a note tagged with an alias of the requested tag, although both skills document a match on the canonical or alias form. (#2209)
|
|
68
|
+
|
|
69
|
+
### 🏗️ Internal features
|
|
70
|
+
|
|
71
|
+
- Adds a section to `_partials/README.md` that states when content becomes a partial and when partials merge, and adds `partial-consumers.unit.test.ts`, which fails when fewer than two files include a partial or when partials with the same includers are neither merged nor listed in that section. (#2183)
|
|
72
|
+
|
|
73
|
+
### ♻️ Refactoring
|
|
74
|
+
|
|
75
|
+
- Inlines the partials that only one file includes into that file, and merges the five ticket partials into `ticket-skeleton` and `ticket-composition`. (#2183)
|
|
76
|
+
|
|
77
|
+
### 🧪 Tests
|
|
78
|
+
|
|
79
|
+
- Replaces six per-doctrine reach test files with `doctrine-reach.unit.test.ts`, which runs the same checks for each entry in the `DOCTRINE_REACH` table in `test-utils/doctrine-reach.ts`. (#2183)
|
|
80
|
+
|
|
81
|
+
### 📦 Dependencies
|
|
82
|
+
|
|
83
|
+
- Move the test runner to Vitest 5 (#2193)
|
|
84
|
+
|
|
85
|
+
Upgrades `vitest` and `@vitest/coverage-v8` from v4 to 5.0.5, and lowers from 7 days to pnpm's 24-hour `minimumReleaseAge` the age at which `nmr upgrade` proposes a third-party release.
|
|
86
|
+
|
|
5
87
|
## 0.2.0 — 2026-10-23
|
|
6
88
|
|
|
7
89
|
### 🎉 Features
|
package/README.md
CHANGED
|
@@ -5,132 +5,28 @@
|
|
|
5
5
|
The CodeAssembly library of agent guidance: rulebooks, skills, and subagents for coding harnesses, which the [`codeassembly`](../agents/README.md) CLI deploys into Claude Code and Rovo Dev.
|
|
6
6
|
|
|
7
7
|
<!-- section:release-notes -->
|
|
8
|
-
## Release notes — v0.
|
|
8
|
+
## Release notes — v0.4.0 (2026-11-02)
|
|
9
9
|
|
|
10
10
|
### 🎉 Features
|
|
11
11
|
|
|
12
|
-
-
|
|
13
|
-
- Adds
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
-
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
- Changes `prepare-prototype-brief` to forbid builders from quoting the brief into the page, to require the demo chrome inside an element marked `data-demo`, and to judge each prototype's product copy against `ui-copy-conventions`. (#2032)
|
|
21
|
-
- Adds the `copy-probe` command to the `index-prototypes` helper, which prints a function for the Playwright MCP's `browser_evaluate` that lists a page's strings of four or more words and skips everything inside `data-demo`. (#2032)
|
|
22
|
-
- Adds the `index-prototypes describe-set` command, which reads a set summary (`shared`, `changes`, `try`) from a JSON file into the manifest; the index page shows that summary below its title, with `try` as a numbered list. (#2034)
|
|
23
|
-
- Adds a repeatable `--note "<label>: <value>"` flag to `index-prototypes register`, which stores each note on the prototype's entry and shows the notes on its card as a definition list in the order given. (#2034)
|
|
24
|
-
- Directs the agent in the `index-prototypes` and `prepare-prototype-brief` skills to choose one list of note labels for the set, to collect a value for each label from every builder, and to write the set summary in a new "Describe the set" step each round. (#2034)
|
|
25
|
-
- Adds drafted titles to `groom-backlog`, which shows a replacement title from the `ticket-assessor` subagent in the digest, applies it with `gh issue edit --title`, and lists "Title" among the parts that the ticket comment reports as revised. (#2038)
|
|
26
|
-
- Adds the `project.maturity` (`hobby`, `early`, `production`), `project.sensitivity` (`low`, `personal`, `confidential`), and `project.audience` (`owner`, `team`, `public`) keys to `.agents/preferences.yaml`, which `derive-session-context` reports as `project_maturity`, `project_sensitivity`, and `project_audience`, or as `null` for a key that the project file does not declare. (#2044)
|
|
27
|
-
- Directs `design-and-plan` and `plan` to treat the declared project stage as the premise of every security, availability, and infrastructure decision, to add machinery beyond that stage only for a named asset or need, and to ask for each undeclared value and then declare it in the project's preferences file. (#2044)
|
|
28
|
-
- Adds the project's declared stage to the design-doc contents that the `williamthorsen-workflow-preferences` rulebook lists for a product's end vision. (#2044)
|
|
29
|
-
- Adds the `check-preferences.mjs` script, which validates a preferences file against the bundled schema, prints its findings as JSON, and exits 1 on an invalid value or a missing required key, reporting an unrecognized key as a warning that names the nearest known key. (#2044)
|
|
30
|
-
- Adds the `refine-prototype` skill, which applies the developer's commands to one prototype page with the development gates off, carries the round's kept and adapted ideas onto it, snapshots each accepted version into the ticket's prototype set, and records every accepted change in a `refinement-log` artifact that the end vision reads. (#2040)
|
|
31
|
-
- Gives each prototype version an id, `{number}.{version}`, that leads the index card and the first line of the page's `data-demo` band, with a `resolve-ids` command on the `index-prototypes` helper that resolves the ids before the prototypes are built and a `--number` flag on `register` that refuses a registration whose number disagrees with the manifest. (#2040)
|
|
32
|
-
- Adds the `assess-usability` skill, available on the Claude harness only, which dispatches a `usability-assessor` subagent for each of three to five lenses in turn and merges their reports into a `usability-findings` artifact that ranks the findings by effect and reach and that `triage-spike-findings` takes as input. (#2045)
|
|
33
|
-
- Adds the `triage-spike-findings` skill, which grades the confidence and value of every item that a findings artifact leaves undisposed, has the new `disposition-challenger` subagent argue against each grade, and then creates the `confidence:`- and `value:`-labelled child tickets under an umbrella ticket and posts every disposition on the triage ticket, on GitHub repositories that have both label families. (#2049)
|
|
34
|
-
- Adds a `--label` argument to `create-ticket`, which applies the given labels on GitHub in addition to the resolved scope and type labels and reports them as skipped on Jira. (#2049)
|
|
35
|
-
- Stops `create-ticket` from asking for confirmation of a relationship supplied through `--parent`, `--blocked-by`, or `--blocking`, and lists that relationship in the completion output. (#2049)
|
|
36
|
-
- Adds the `check-site --target <url-or-host>` subcommand to `manage-jira-ticket.mjs`, which prints `acli`'s active site and the ticket's site as JSON and, when they differ, exits non-zero and names the `acli jira auth switch` command that makes the ticket's site active. (#2052)
|
|
37
|
-
- Adds the `jira-clients` guidance hook to `update-jira-ticket`, through which a machine adds its own Jira client, with the sites that it reaches and its rank, to the clients that the Jira skills read and create through. (#2052)
|
|
38
|
-
- Adds an "External programs" section to the `testing-conventions` skill, which directs that code reach git or another external program through an adapter received as a dependency, that tests of that code pass a fake adapter, and that only the adapter's own test run the real program. (#2055)
|
|
39
|
-
- Adds an "External programs" section to the `typescript-testing-conventions` skill, with an example of an adapter type, a real adapter used as a parameter default, and a test that passes an object literal as the fake, and states a preference for that parameter over `vi.mock`. (#2055)
|
|
40
|
-
- Rewrites the description of the `testing-conventions` skill to name how a test reaches git and other external programs, and to direct agents to consult the skill before writing or changing a test. (#2055)
|
|
41
|
-
- Move kb's git calls behind an injectable adapter (#2077)
|
|
42
|
-
|
|
43
|
-
Adds an optional `git` parameter to `check`, `enumerateNotes`, and `enumerateNotePaths` in `@williamthorsen/kb/check`, which takes a `KbGit` adapter so that a consumer's tests can run these functions without a real git repository. The change also routes every git call inside kb through one such adapter and replaces the repositories that kb's tests built with a fake adapter.
|
|
44
|
-
|
|
45
|
-
- Changes the next-steps menus of the planning, implementation, and review skills to name each skill in the harness's own invocation syntax, such as `/refine-plan` on Claude Code and `!refine-plan` on Rovo, so that a user can paste an option line without retyping it. (#2084)
|
|
46
|
-
- Adds a "Where a test goes" section to the `testing-conventions` skill, which directs each case to the cheapest tier that can observe it, limits an expensive tier (one that spawns a process, starts a runtime, or builds a full fixture) to one smoke example per entry or verb, and requires a change to delete the higher-tier examples that its cheaper coverage supersedes and to justify each expensive-tier example that it adds. (#2086)
|
|
47
|
-
- Adds a "Test placement" section to the `review-criteria` skill, which classes as a Warning an added expensive-tier example that a cheaper tier could observe, and also a higher-tier suite that the change superseded but kept. (#2086)
|
|
48
|
-
- Changes the test criterion in `ticket-criteria-conventions` and `plan-template` to ask for coverage at the cheapest tier that observes the behavior, rather than for coverage by tests alone. (#2086)
|
|
49
|
-
- Changes the `accessibility-conventions` and `shared-data-conventions` rulebooks to `skill` delivery alone, so that they no longer appear in every session's guidance file and are reached through `consult-accessibility-conventions` and `consult-shared-data-conventions`, and adds an "Interfaces" criterion to `review-criteria` that points a review of colour tokens, text styles, pages, or UI components to `accessibility-conventions`. (#2087)
|
|
50
|
-
- Adds an "Always-loaded context" section to `review-criteria`, which classifies a change as a Warning when it makes a rulebook ambient or grows an `AGENTS.md`, a `CLAUDE.md`, or another file loaded at session start, unless nearly every session needs the content. (#2087)
|
|
51
|
-
- Updates `codeassembly-content-specification` to version 30, which states that `delivery` is required and that `ambient` fits only content that nearly every session needs. (#2087)
|
|
52
|
-
- Adds a rule to `prepare-prototype-brief` that directs the brief's author to describe an audience-facing view by what the audience sees, and adds a line to the brief check that has the author rewrite phrases such as "mystery" and "unknown to" without the withheld information. (#2089)
|
|
53
|
-
- Makes `create-gh-pr` assign each pull request that it creates to the authenticated `gh` user, record the applied assignee in the `pull-request` artifact, and report the assignee as skipped when GitHub does not apply it. (#2090)
|
|
54
|
-
- Adds setup rules to the `testing-conventions` skill that count a database engine as an expensive tier, call for the cheapest setup that fits the time budget, keep setup cost independent of the number of test files, and reject a raised hook timeout as a fix. (#2092)
|
|
55
|
-
- Adds a "Code that uses a database" section to the `testing-conventions` skill, which limits database tests to code whose subject is SQL, directs logic that only passes through SQL to a fake client or a mocked module boundary, and rules out a test per constraint. (#2092)
|
|
56
|
-
- Adds four Warnings to the `review-criteria` skill for database and setup defects in tests that the change adds, splits, or modifies, and changes the split that it proposes for a grown test file to share the file's expensive setup first. (#2092)
|
|
57
|
-
- Adds the `cli-conventions` rulebook, delivered as the `consult-cli-conventions` skill, which states that a CLI printing a doc as a help topic renders a link to another topic as the `<bin> help <topic>` command, renders any other link as its absolute URL, and accepts the doc's file stem as a name for the topic. (#2093)
|
|
58
|
-
- Adds `cli-conventions` to the `recommended` collection, so that a project declaring that collection receives the rulebook. (#2093)
|
|
59
|
-
- Adds `--repo OWNER/REPO` to `/create-ticket`, which files the ticket in that GitHub repository and resolves its title format, reference prefix, scope, and labels from the configuration on that repository's default branch. (#2094)
|
|
60
|
-
- Adds `--project-root <dir>` to `describe-change render-titles` and `resolve-labels`, which then read `.agents/preferences.yaml` and `.meta/label-map.json` from that directory in place of the invoking repository's root. (#2094)
|
|
61
|
-
- Makes `describe-change resolve-labels` warn on stderr about each type or scope that a configured label map does not define, where it previously omitted the label without a message. (#2094)
|
|
62
|
-
- Adds a `medium` input to `assess-usability`. When set to `cli`, each `usability-assessor` lens runs the built binary in its own scratch git repository and saves text transcripts as evidence, and the styling-and-access lens is replaced by an output-and-access lens that checks `NO_COLOR`, piped output, 80-column width, and help and error text. (#2095)
|
|
63
|
-
- Orders the `ticket` items of `triage-spike-findings` by value, then confidence, with record order breaking ties, when the skill creates the child tickets and when it lists them in the checkpoint table, the dispositions comment, and the report, so that the children's issue numbers follow that order. (#2096)
|
|
64
|
-
- Adds a rule to the "Technical recommendations" guidance that directs an agent to name the best-practice solutions to a design problem and the conditions under which each one fits before it weighs options, to label an option that departs from all of them as non-standard with the reason that none fits, and to recommend revising an existing API rather than an addition that works around its contract. (#2098)
|
|
65
|
-
- Includes the "Technical recommendations" guidance in the `ticket-assessor` subagent, which validates a ticket's proposed approach. (#2098)
|
|
66
|
-
- Extends the `cli-conventions` rulebook from help topics to the whole interface of a command-line tool in any language, adding rules for `--help` on every command and subcommand, an exit-code table, error messages that name the fix, and step and outcome reports for commands that change state. (#2099)
|
|
67
|
-
- Reduces the `shell-conventions` rulebook to how a bash script implements the `cli-conventions` rules, and changes its `show_usage` template to write requested help to stdout and to exit 2 on an unknown command. (#2099)
|
|
68
|
-
- Adds a "DOM environment" section to the `typescript-testing-conventions` skill, which directs a TypeScript test that renders into a DOM to run under happy-dom and allows jsdom only at an opt-in whose comment names the behavior that happy-dom lacks. (#2101)
|
|
69
|
-
- Adds the `codeassembly-validate-preferences` bin to `codeassembly-guidance`, which validates each named preferences file against the bundled schema without network access, reports a missing or unparsable file as an error, prints text or one JSON object per file under `--json`, and treats warnings such as an unrecognized key as failures under `--strict`. (#2103)
|
|
70
|
-
- Renames the deployed `check-preferences.mjs` helper to `validate-preferences.mjs` and gives it the bin's behavior: several files per run, text output by default, and the `--json`, `--strict`, and `--help` options. (#2103)
|
|
71
|
-
- Directs the agent, in the `williamthorsen-collaboration-preferences` rulebook and the option-format rule, to start each line that states a decision awaiting the checkpoint with ⏳, in a turn's narrative as well as in the plan and spike templates' `## Decisions taken` section, where the marker replaces the `(provisional)` parenthetical. (#2104)
|
|
72
|
-
- Extends `triage-spike-findings` to have the agent decide the blockers of each ticket that it creates, create every blocker before the tickets that it blocks, link them through `create-ticket --blocked-by`, and list them in a "Blocked by" column of the dispositions comment. (#2105)
|
|
73
|
-
- Adds to `williamthorsen-ticketing-preferences` a rule to record a blocker whenever there is some probability that one ticket affects another and should land first, including when one ticket's design takes another ticket's outcome as an input. (#2105)
|
|
74
|
-
- Adds a directive to the "Handoffs" section of `williamthorsen-collaboration-preferences` that tells the agent to hand over a check of more than one command as one paste-ready script, which cleans up after itself and prints only the facts that the agent needs, and to confirm which machine its commands run on, such as by comparing `hostname`, before it runs or hands over a check of a GUI application. (#2106)
|
|
75
|
-
- Adds to `accessibility-conventions` the states that every clickable element shows (a pointer cursor, a hover change, and a focus indicator that meets 3:1 non-text contrast), and requires a browser check of each change to a visible component, with a report that the check did not run when a browser is unavailable. (#2109)
|
|
76
|
-
- Directs `implement-plan` to run that browser check for any change to a visible component, whether or not the plan lists it, and to report what the check found, and adds the interaction states and the check to the plan template's interface guidance. (#2109)
|
|
77
|
-
- Directs `review-criteria` to check each new or changed interactive element in a browser rather than by reading the diff alone, and adds the outcome of that check to the technical assessment in both `review-branch` report templates. (#2109)
|
|
78
|
-
- Makes `design-and-plan`, `plan`, and `refine-plan` report each open blocker of the resolved GitHub or Jira ticket by reference and title, and then continue. (#2113)
|
|
79
|
-
- Makes `implement-plan` ask the user to confirm before it starts the first task when the governing ticket has an open blocker. (#2113)
|
|
80
|
-
- Extends the blocker check to a ticket artifact, which the skills check against the remote ticket named by its `ticket_ref` frontmatter. (#2113)
|
|
81
|
-
- Lets `refine-plan` resolve a Jira ticket by URL or key through the Jira clients that the ticket source resolution ranks, where it previously fetched a Jira URL as a web page. (#2113)
|
|
82
|
-
- Adds a rule to `williamthorsen-tooling-preferences` that directs an agent to log into a local instance of the app under work without asking the developer, and to set a development credential in an untracked local config file when the app needs one, which the rulebook does not count as minting a credential. (#2115)
|
|
83
|
-
- Limits the login that the handoff ladder in `williamthorsen-collaboration-preferences` names among the resources that an agent asks the developer to supply to a login to a remote service, which excludes an app's local development login. (#2115)
|
|
84
|
-
- Adds a step to `design-and-plan`, `plan`, `refine-plan`, and `implement-plan` that checks the branch against the remote's default branch before the work starts, fast-forwarding a branch that lacks commits and uncommitted changes of its own and otherwise listing the gained commits and asking whether to bring them in. (#2119)
|
|
85
|
-
- Adds the `check-branch-currency.mjs` script, which fetches the remote's default branch and reports as JSON how far the checked-out branch is behind and ahead of it, whether its tree is clean, and which gained commits touch the paths passed with `--path`. (#2119)
|
|
86
|
-
- Adds an "Authorship" section to the shared `AGENTS.md`, which states that a creator, reporter, or author field shows the account that made an item rather than who wrote it, and forbids inferring from that field that the developer wrote the item. (#2120)
|
|
87
|
-
- Changes `ticket-evaluation.md` to tell the agent to treat a ticket's content as unsourced, whichever account created the ticket, until the agent traces the content to a source. (#2120)
|
|
88
|
-
- Adds a "Subcommand names" section to the `cli-conventions` rulebook, which requires a subcommand that acts to name its action and its object, prescribes a flat verb-object name such as `show-instance-page` while the object has one action and a noun group such as `instance-page show` once it has several, and rejects an existing name that breaks these rules as precedent. (#2121)
|
|
89
|
-
- Makes `kb-curate` report `missing-destination` when `--kb` is absent and no `.kb/` is discoverable, and `no-default` when `--kb @default` is given without a configured `default_kb`, where both cases previously returned `no-kb-resolvable`. (#2122)
|
|
90
|
-
- Makes `kb-edit` report a note outside any discoverable `.kb/` as `missing-destination` instead of `no-kb-resolvable`, the code that `kb-add` uses for the same condition. (#2122)
|
|
91
|
-
- Rewrites the `.editorconfig` bullet in the shared "Style" guidance to direct agents to follow `.editorconfig` and to fill new comments to the `max_line_length` that it sets. (#2123)
|
|
92
|
-
- Adds rules to `cli-conventions`, each with an example, on when a behavior is a subcommand rather than an option, standard option names such as `--config`, `--dry-run`, and `--write`, the order in which settings resolve, which commands write by default, `--json` output, color, error messages that suggest the nearest valid name and never take a secret as an argument, and keeping a command's logic apart from its presentation. (#2134)
|
|
93
|
-
- Changes the exit code that `cli-conventions` assigns to a usage error, such as bad input or an unknown command or option, from 1 to 2, and adds exit code 1 for a check that ran and found problems. (#2134)
|
|
94
|
-
- Changes the default exit code of the `show_usage` template in `shell-conventions` from 1 to 2, so that a bare `show_usage` call covers every usage error, including an unknown command. (#2134)
|
|
95
|
-
- Makes `select-lede-exemplars.mjs` act on the breaking marker, which it previously discarded: An unmarked request no longer returns a breaking record, and a request marked by a `!` on `--type` returns breaking records before non-breaking ones within each widening step. (#2136)
|
|
96
|
-
- Adds a `--breaking` flag to `select-lede-exemplars.mjs`, which marks a `--type` or `--tier` request as breaking, and adds a `breaking` field to the JSON output, which reports whether the request was marked. (#2136)
|
|
97
|
-
- Changes the `entry-drafter` subagent to request exemplars once per pair of work type and breaking marker, passing `--breaking` for a breaking entry, rather than once per work type. (#2136)
|
|
98
|
-
- Defines the members of the `triage` collection with `'@unclaimed'`, so that `codeassembly` deploys a newly added library artifact through `triage` until the artifact is promoted to another collection or declares `standalone:`. (#2137)
|
|
99
|
-
- Adds the `overused-word` rule to the `revise-prose` sweep, which reports one candidate per sentence that contains a word from the plain-speech calibration's "Words to look for" list or an inflection of one, lists the matched words, and leaves `prose-reviser` to repair the site or reject a use in a sense that the list keeps. (#2139)
|
|
100
|
-
- Adds the `check-prose.mjs` script, which runs every `revise-prose` detector over one Markdown file at any path without reading or writing the sweep record, and exits 1 when it reports candidates and 2 when it cannot read the file. (#2141)
|
|
101
|
-
- Adds a writing-rules check to step 6 of `summarize-change`, which runs `check-prose.mjs` over the lede, each entry's `text` and `migration`, and the "Why" section, and directs the session to redispatch the `entry-drafter` with the new `writing-rule` rejection code for a confirmed violation in a drafted passage. (#2141)
|
|
102
|
-
- Extends `revise-comments` to add a missing description to each function, method, class, and component, test helpers included, and to rewrite a description that misstates its code, with an instruction to ask the user first when the code rather than the description could be wrong. (#2146)
|
|
103
|
-
- Adds a "Test data" section to the `testing-conventions` skill, which requires each test to use the smallest data that proves its behavior and requires code that reads data from a module-level singleton to take it as a parameter or from a context whose default is the real value. (#2167)
|
|
104
|
-
- Extends the "Fix the design, not the timeout" rule in `testing-conventions` from a hook's timeout to a test's and a tier's timeout, set in a test or in config, and permits a raise only when smaller data, injection, and shared setup do not apply and the plan or the pull-request description states why. (#2167)
|
|
105
|
-
- Adds a Warning to `review-criteria` for a raised hook, test, or tier timeout, which a stated reason does not exempt, and a Warning for a test that renders or builds production-scale data, replacing the narrower "A raised hook timeout" item. (#2167)
|
|
12
|
+
- Adds the `curate-feedback` skill, which has `feedback-coverage-judge` subagents sort each open feedback event into covered, duplicate, obsolete, or kept against guidance pinned at a commit, and then, after approval or under `--apply`, marks every event that is not kept through `kb-update-events` and records the run in a `feedback-curation` artifact. (#2231)
|
|
13
|
+
- Adds each covered entry's quote to the `feedback-curation` artifact's events table and to the approval table that `curate-feedback --list` presents, so that the developer can check every covered verdict against its stating sentence before approving the marks. (#2236)
|
|
14
|
+
|
|
15
|
+
### 🪦 Removed
|
|
16
|
+
|
|
17
|
+
- Remove the factory and the demos (#2234)
|
|
18
|
+
|
|
19
|
+
Removes the dormant factory visualization package and the catwalk demos, together with the docs, repo-local skills, dependencies, and configuration that only they used. Adds to `docs/repository-split.md` the command that finds the last commit containing the factory, which is the commit from which a revival restores it.
|
|
106
20
|
|
|
107
21
|
### 🐛 Bug fixes
|
|
108
22
|
|
|
109
|
-
- Fixes the issue that `
|
|
110
|
-
- Fixes the issue that
|
|
111
|
-
- Fixes the issue that `
|
|
112
|
-
- Fixes the issue that `
|
|
113
|
-
-
|
|
114
|
-
|
|
115
|
-
|
|
116
|
-
- Fixes the issue that ticket resolution, `update-jira-ticket`, and `create-ticket` reported a Jira ticket on another site as missing, by directing each to run `manage-jira-ticket.mjs check-site` before calling `acli` and to report the wrong site and the `acli jira auth switch` command instead. (#2052)
|
|
117
|
-
- Fixes the issue that the `live-worktree-policy` rulebook named the removed `list-repos --tag live` command for listing the repos tagged `live`, and replaces it with `thor-repo list --tag live`. (#2053)
|
|
118
|
-
- Fixes the issue that a `summarize-change` redispatch did not send `entry-drafter` the type corrected by the audit, which left the drafter to rewrite the entry in the form of the old type. (#2058)
|
|
119
|
-
- Fixes the issue that the artifact guidance never stated what the artifact directory is for, by stating that it is the developer's audit trail rather than a source of truth, directing durable instructions to the repository or to a skill or rulebook, and telling the agent to verify what a search of artifacts returns against the repository, the tickets, and the pull requests. (#2070)
|
|
120
|
-
- Fixes the issue that `williamthorsen-workflow-preferences` did not say that the branch and worktree for a ticket's work are settled, which left agents asking the developer which one to use. (#2082)
|
|
121
|
-
- Fixes the issue that `design-and-plan` ended a session that split a ticket without a launch prompt for each resulting ticket, and that its `Next action` menu could offer to implement an umbrella's child in the umbrella's worktree. (#2083)
|
|
122
|
-
- Fixes the issue that the `triage-spike-findings` helper's `check-labels` command crashed with "e is not a function" instead of running `gh label list`, which stopped the skill before triage began. (#2085)
|
|
123
|
-
- Fixes the issue that `williamthorsen-collaboration-preferences` and the `action-items` and `option-format` partials stated many directives in the indicative, which hid whether the agent was to act, by restating them as imperatives addressed to the agent. (#2106)
|
|
124
|
-
- Documents in the `kb-add` skill the `readonly-kb` error code, which its helper already returned, and tells the agent to have the user choose a writable KB. (#2122)
|
|
125
|
-
- Fixes the issue that the rulebooks, skills, subagents, and partials in `codeassembly-guidance` contained sentences that the library's own current writing rules flag, such as figurative verbs, "no" used as a determiner, and reduced object relatives, and keeps each rulebook's `version` because the repairs do not change what it asks. (#2130)
|
|
126
|
-
- Fixes the issue that messages printed by `describe-change`, `index-prototypes`, `resolve-review-run`, `revise-prose`, and `triage-spike-findings` broke the writing rules, for example by saying `no manifest in` a directory rather than that the directory does not contain a manifest, and keeps each message's error code. (#2132)
|
|
127
|
-
- Fixes the issue that the artifact conventions told agents to run `export-ai-artifacts.sh`, which has been deleted, and called a git-ignored `base_dir` the default when the documented default is `~/ai-artifacts`. (#2135)
|
|
128
|
-
- Fixes the issue that `revise-prose` reported a file as swept after its prose was edited, by recording a hash of each file's extracted prose in `.agents/revise-prose.yaml` and reporting the file as unswept when the current hash differs. (#2143)
|
|
129
|
-
- Fixes the issue that the leader check in the option-format contract and the `williamthorsen-collaboration-preferences` rulebook did not cover gated decisions, and adds a first step that searches each alternative for a disqualifying cost, including one that follows from the work's constraints and acceptance criteria. (#2145)
|
|
130
|
-
|
|
131
|
-
### ⚡ Performance
|
|
132
|
-
|
|
133
|
-
- Shortens the `index-prototypes` skill by 675 bytes, cutting explanations that a neighboring sentence restated, and leaves its behavior unchanged. (#2040)
|
|
23
|
+
- Fixes the issue that the `feedback-coverage-judge` subagent of `curate-feedback` marked a feedback event `obsolete` when the change that removed the event's target had renamed or moved it, or had named a replacement for it. (#2233)
|
|
24
|
+
- Fixes the issue that `curate-feedback validate` accepted a `covered` entry after checking only that the cited guidance file existed, by requiring a verbatim `quote` of the stating sentence and rejecting the entry when the file at the pin does not contain it, ignoring differences in whitespace and in `*`, `_`, and backtick markers. (#2236)
|
|
25
|
+
- Fixes the issue that `triage-feedback` ranked a feedback cluster by its events even when all of them predated a change to the guidance that governs its lesson, and directs the skill and its `feedback-triage-challenger` subagent to check that guidance's commit history and set such a cluster to `low` unless evidence shows the failure recurring under the changed guidance. (#2243)
|
|
26
|
+
- Fixes the issue that `triage-feedback` and `triage-spike-findings` accepted a defense against the challenger that rested on grounds other than the evidence named by the challenger's argument. (#2243)
|
|
27
|
+
- Remove the unshipped `source` export condition from the published packages (#2244)
|
|
28
|
+
|
|
29
|
+
Removes the `source` export condition from `codeassembly`, `@williamthorsen/kb`, and `codeassembly-run-core`, because it pointed at TypeScript files that their tarballs don't contain, so that a consumer that enables the condition resolves the shipped `dist/` output instead of failing.
|
|
134
30
|
<!-- /section:release-notes -->
|
|
135
31
|
|
|
136
32
|
## Using the library
|
|
@@ -177,7 +73,7 @@ Agent behavior is configured through `.agents/preferences.yaml` files. The resol
|
|
|
177
73
|
2. **Global**: `~/.agents/preferences.yaml` in the user's home directory (personal defaults)
|
|
178
74
|
3. **Default**: built-in fallback (documented per key in [Preferences](docs/preferences.md))
|
|
179
75
|
|
|
180
|
-
Project-level values take precedence over global. An explicitly empty value at the project level (e.g., `title_format: ''`) overrides a non-empty global value.
|
|
76
|
+
Project-level values take precedence over global, key by key within each section: A project `ticket` section that sets only `title_format` keeps the global `ticket.base_url`. A map-valued key inside a section, such as `artifacts.paths` or `repository.default_remote`, is one value, which a project value replaces whole. An explicitly empty value at the project level (e.g., `title_format: ''`) overrides a non-empty global value.
|
|
181
77
|
|
|
182
78
|
The package publishes a JSON Schema for the file; [Schemas](docs/schemas.md) gives its identifier and versioning. To validate preferences files in a repository's own checks, install this package and run its bin on them; [Validation](docs/preferences.md#validation) states its options and rules.
|
|
183
79
|
|
|
@@ -193,3 +89,6 @@ codeassembly-validate-preferences --strict .agents/preferences.yaml
|
|
|
193
89
|
- [Prototype index helper](docs/index-prototypes-helper.md): the helper that the `index-prototypes` skill runs.
|
|
194
90
|
- [Guidance streamlining helper](docs/streamline-guidance-helper.md): the helper that the `streamline-guidance` skill runs.
|
|
195
91
|
- [Findings triage helper](docs/triage-spike-findings-helper.md): the helper that the `triage-spike-findings` skill runs.
|
|
92
|
+
- [Code-health helper](docs/assess-code-health-helper.md): the helper that the `assess-code-health` skill runs.
|
|
93
|
+
- [Feedback triage helpers](docs/triage-feedback-helper.md): the helpers that the `triage-feedback` skill runs.
|
|
94
|
+
- [Feedback curation helper](docs/curate-feedback-helper.md): the helper that the `curate-feedback` skill runs.
|