@warren-dean/code-kit 0.26.1 → 0.27.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/.claude-plugin/marketplace.json +1 -1
- package/.claude-plugin/plugin.json +1 -1
- package/CHANGELOG.md +24 -0
- package/README.md +5 -3
- package/bin/code-kit.mjs +269 -52
- package/hooks/act.mjs +14 -5
- package/hooks/guard-bash.mjs +76 -17
- package/hooks/lib/checkout.mjs +105 -0
- package/hooks/lib/checks.mjs +34 -8
- package/hooks/lib/config.mjs +5 -2
- package/hooks/lib/dependencies.mjs +4 -0
- package/hooks/lib/designs.mjs +137 -0
- package/hooks/lib/events.mjs +9 -4
- package/hooks/lib/hook.mjs +41 -1
- package/hooks/lib/next.mjs +33 -5
- package/hooks/lib/plan.mjs +103 -15
- package/hooks/lib/queue.mjs +86 -1
- package/hooks/lib/regression.mjs +54 -44
- package/hooks/lib/rules.mjs +63 -20
- package/hooks/lib/team.mjs +27 -1
- package/hooks/lib/timeline.mjs +3 -20
- package/hooks/lib/verify.mjs +37 -4
- package/hooks/lib/worktrees.mjs +18 -1
- package/hooks/mod/board.mjs +54 -59
- package/hooks/mod/characters.mjs +96 -174
- package/hooks/mod/loop.mjs +44 -1
- package/hooks/mod/register.mjs +96 -8
- package/hooks/mod/surface/character.mjs +1 -1
- package/hooks/mod/view.mjs +8 -0
- package/hooks/stop-check.mjs +6 -1
- package/package.json +1 -1
- package/skills/design/SKILL.md +36 -7
- package/skills/dispatch/SKILL.md +1 -0
- package/skills/review/SKILL.md +2 -1
- package/skills/spec-design/SKILL.md +1 -1
- package/skills/status/SKILL.md +1 -1
- package/templates/agent.md +2 -1
|
@@ -9,7 +9,7 @@
|
|
|
9
9
|
"name": "code-kit",
|
|
10
10
|
"source": "./",
|
|
11
11
|
"description": "Keeps AI coding agents inside your project's rules, from idea to merged code: spec design, lanes, layer rules, protected paths with an approval log, spec-check and design gates, proof-before-finish checks, dispatch, review, build status and CI verification, configured per project from its docs",
|
|
12
|
-
"version": "0.
|
|
12
|
+
"version": "0.27.0",
|
|
13
13
|
"category": "development",
|
|
14
14
|
"tags": ["guardrails", "architecture", "lanes", "layers", "spec-driven", "ci", "multi-agent"],
|
|
15
15
|
"license": "MIT"
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "code-kit",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.27.0",
|
|
4
4
|
"description": "Keeps AI coding agents inside your project's rules, from idea to merged code: spec design, lanes, layer rules, protected paths with an approval log, spec-check and design gates, proof-before-finish checks, dispatch, review, build status and CI verification, configured per project from its docs",
|
|
5
5
|
"author": {
|
|
6
6
|
"name": "Warren Langeveldt"
|
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,30 @@
|
|
|
2
2
|
|
|
3
3
|
What changed in each release of code-kit, newest first. Versions follow the plugin manifest and the npm package `@warren-dean/code-kit`. Each release is also on [GitHub Releases](https://github.com/warrendeanlangeveldt/code-kit/releases).
|
|
4
4
|
|
|
5
|
+
## 0.27.0 (2026-10-30)
|
|
6
|
+
|
|
7
|
+
Fixes for what projects reported: the loop respects Claude's usage limit, merges land as they were verified, claims end with their stories, and approved designs reach lanes as files.
|
|
8
|
+
|
|
9
|
+
- **Usage limits.** When Claude's usage limit stops the lead, the loop now waits until the limit resets instead of prompting into it, and the band says so, with **Try now**. With no reset time, it retries after 5 minutes, doubling up to an hour. A lane agent stopped by the limit isn't taken as finished: it keeps its lane, its story stays in progress, and its finish isn't checked.
|
|
10
|
+
- **The loop** no longer repeats steps it has already asked while nothing in the project has changed. It doesn't send a step it worked out while the lead's turn began, so a branch you just dropped from the queue isn't put up to merge. It carries on a lane agent at its context limit only when the agent says it isn't finished.
|
|
11
|
+
- **The merge queue** verifies each branch as it will land, merged with the base in a fresh checkout that has its own installs. A merge already running isn't started again or asked for. `queue add <branch> --with <other>` makes branches that only work together wait for each other and merge as one. `merge <branch>` marks its queue entry as merged.
|
|
12
|
+
- **Claims.** When a story merges, its claim is released on GitHub as well as on the hub, and claims stuck on merged stories are cleared.
|
|
13
|
+
- **Approvals.** When merges are delegated, the lead still needs your approval to change what's yours. Every commit is judged, including `git -C`, and a commit chained after a command that writes files is refused. A refusal says when the approval ran out or which commit used it up. A commit stopped by the secrets scan doesn't use one up, and a request is no longer closed by a commit made just before it.
|
|
14
|
+
- **Test checks.** `expect.poll` and `expect.soft` count as assertions. A branch deleting or reworking tests it added itself isn't weakening tests. A fix made entirely in tests (a flaky test, a broken helper) passes the fix check. A fix's proof that a typecheck failure hid is found.
|
|
15
|
+
- **verify** no longer counts files the branch holds exactly as the base does. A check's long output doesn't fail it, because its exit code decides. Installs inside a container (`docker run`, podman) aren't the project's dependencies. `.mcp.json` belongs to the lead.
|
|
16
|
+
- **Plans and commands.** A story marked `**Status:** dropped` is never dispatched or waited on. A story whose lane is building it again isn't offered for review. `ask --help` and `ask list` behave as commands. `git merge-base`, `merge-tree` and `commit-tree` aren't read as merges or commits.
|
|
17
|
+
- **Designs handed over (spec 24).** An approved design is now files in `design/` (each state's code and a PNG, with their hashes), so a lane builds from exactly what you approved. Committing the register is refused while a file is missing or changed, or a state the spec lists has no design. `code-kit designs <story>` lists a story's designs, and review compares each built screen with its design. `next` asks once to export designs that are still only in a design tool (`/code-kit:design --hand-over`).
|
|
18
|
+
- After updating, `next` asks to refresh each project's lane-agent instructions.
|
|
19
|
+
|
|
20
|
+
## 0.26.2 (2026-10-26)
|
|
21
|
+
|
|
22
|
+
The lanes pane tells the truth about what's being built, and is easier to read.
|
|
23
|
+
|
|
24
|
+
- A lane no longer says "building" when nothing is building it. A story whose branch had merged, but whose line in the plan hadn't moved on, read as in progress forever and held its lane, so nothing new was sent to it. Now a story is in progress only while an agent's claim names it or you have its branch checked out. One whose work has merged counts as done, and `code-kit next` lists the plan lines that are out of date. One whose agent stopped before its first commit is ready again, and `next` sends it to a fresh agent and says why.
|
|
25
|
+
- In a project with a long history, the plan's git reads no longer come back empty.
|
|
26
|
+
- The lane characters are smaller, 8 by 8 pixels (four rows), and every pose is redrawn. A resting lane shows a "z".
|
|
27
|
+
- The keys line shows each key once (`j: down · k: up · ⏎: open · f: filter · l: journal`), and a lane's action buttons no longer show their key twice.
|
|
28
|
+
|
|
5
29
|
## 0.26.1 (2026-10-26)
|
|
6
30
|
|
|
7
31
|
`/lanes` opens in large projects again.
|
package/README.md
CHANGED
|
@@ -214,7 +214,7 @@ spec-design works an idea into a specification with you before any code exists.
|
|
|
214
214
|
|
|
215
215
|
It writes `docs/brief.md` (with the decision log and open questions), `docs/specs/NN-<area>.md`, `docs/architecture.md`, `docs/standards.md`, `docs/principles.md` and `docs/plan.md`. Those are exactly what `/code-kit:init docs/` turns into lanes, layers and standards, and what lanes spec-check against. Run it again to resume where it left off, to change a decision, or to spec a new feature in an existing codebase.
|
|
216
216
|
|
|
217
|
-
Requirements are headings (`### BOOK-4 Cancel a booking`). Stories are `### ST-12` headings in the plan with `**Lane:**`, `**Requirements:**`, `**Depends on:**` and `**Status:**` lines (`templates/plan.md`). The lane `lead` marks the lead's own stories, such as contracts and spikes, which the lead builds itself instead of dispatching; the lane `design` marks a design story, which the lead designs with you (`/code-kit:design`) before any screen that depends on it is built; `**Requirements:** none` marks a story that delivers no requirement. Those two formats are what the build loop below runs on.
|
|
217
|
+
Requirements are headings (`### BOOK-4 Cancel a booking`). Stories are `### ST-12` headings in the plan with `**Lane:**`, `**Requirements:**`, `**Depends on:**` and `**Status:**` lines (`templates/plan.md`). The lane `lead` marks the lead's own stories, such as contracts and spikes, which the lead builds itself instead of dispatching; the lane `design` marks a design story, which the lead designs with you (`/code-kit:design`) before any screen that depends on it is built; `**Requirements:** none` marks a story that delivers no requirement. `**Status:** dropped` takes a story out of the plan without deleting it (folded into another, or no longer wanted): it's never dispatched, never waited on, and covers no requirement. Those two formats are what the build loop below runs on.
|
|
218
218
|
|
|
219
219
|
## Set up a project
|
|
220
220
|
|
|
@@ -463,6 +463,7 @@ code-kit worktrees discard <branch> # the person's, from the band: remove a mer
|
|
|
463
463
|
code-kit instructions [--write] [--json] | instructions show lead|lane [<lane>] # code-kit's part of CLAUDE.md and the lane agents: where each stands, brought up to date, or printed
|
|
464
464
|
code-kit standards [--json] [--for <path>...] # the project's standards with any its organisation's provider supplies, and what's wrong with them; --for keeps the ones for those files' layers
|
|
465
465
|
code-kit trace <path>... [--json] # what a file is for: requirements, lane, layer rules
|
|
466
|
+
code-kit designs [<story>] [--json] # the approved designs: a story's screens' files, every state, or each entry and what's wrong with it
|
|
466
467
|
code-kit merge <branch> --delegated|--person [--into branch] # merge a branch that passes verify: the lead where approvals.delegate.merge is on, or the person
|
|
467
468
|
code-kit publish --delegated|--person # put what's merged into the base onto the remote's, as branches.publish says
|
|
468
469
|
code-kit replay <story> [--json|--brief] # a story's state rebuilt from its event log: its phase, last commit, tests, what's left open
|
|
@@ -489,6 +490,7 @@ code-kit settings [--json] # the harness setti
|
|
|
489
490
|
code-kit settings set <key> <value> --reason "…" # change one, as the person (approvals.<name> lead|person among them): written to the config and logged as a kit approval
|
|
490
491
|
code-kit queue [--json] # the merge queue: branches whose review passed, in order
|
|
491
492
|
code-kit queue add|drop <branch> # the lead queues a branch at the commit its review passed, or takes it out
|
|
493
|
+
code-kit queue add <branch> --with <branch>[,<branch>] # a branch that only lands together with others: merged as a group once all are queued
|
|
492
494
|
code-kit queue rules # the lead puts the approved rules onto a base that has none yet (a project set up before 0.8.0)
|
|
493
495
|
code-kit queue merge --delegated|--person # merge the head at the commit its review passed, verified against the base as it is now; a conflict or failed verify sends it back to its lane, and a branch that moved since its review leaves the queue to be reviewed again
|
|
494
496
|
code-kit loop [--json] # whether the person paused the lead loop; other tools' background work pauses with it
|
|
@@ -530,7 +532,7 @@ code-kit approve <name>... --reason "…" [--lane name] [--delegated [--story ST
|
|
|
530
532
|
| `docs.principles`, `docs.plan` | no | The engineering principles and the implementation plan |
|
|
531
533
|
| `docs.decisions` | no | Where agreed intents are recorded as numbered decision records (`code-kit intend record`); default `docs/decisions` |
|
|
532
534
|
| `docs.standards` | no | The project's standards (spec 22), default `docs/standards.md`: each a `### <id> <title>` heading with `level` (required or recommended), `applied` (enforced, checked or advice), `layers`, `why`, `source` and, when enforced, `enforced by` naming the layer rule, protected path, check or shell rule that refuses a breach. The id's prefix is its category: `PRI-` principles, `PAT-` patterns, `ARC-` architecture, `CON-` conventions, `POL-` policies. Each lane agent is given the ones for its layers; a refusal from an enforcing rule names the standard; reviews check the checked ones. Protect the file with the `standards` approval: removing a standard, or weakening a required one, always needs the person's, whatever is delegated |
|
|
533
|
-
| `lead.paths` | yes | What the main session writes. `.claude/**`
|
|
535
|
+
| `lead.paths` | yes | What the main session writes. `.claude/**` and `.mcp.json` are always added. |
|
|
534
536
|
| `lead.outside` | no | Paths outside the repository the lead may write, e.g. `../shared-lib/**`. Claude's memory and scratchpad are always included. |
|
|
535
537
|
| `anyActor` | no | Paths every writer may change (e.g. the lockfile), read-only agents included. `.claude/state/**` is always included. An entry may be `{ "glob", "reviewer" }` to name the lane (or `"lead"`) that reviews changes to it; otherwise the lead reviews them, and `who` and `trace` say so. |
|
|
536
538
|
| `lanes.<name>` | yes (may be `{}`) | `{ agent, paths, exclude?, owners? }`: the agent name maps a subagent to its lane; `owners` (GitHub handles) are the people whose sessions work it, in a team (needs `team`). A worktree with a `.lane` file holding the lane name makes the main session that lane. |
|
|
@@ -542,7 +544,7 @@ code-kit approve <name>... --reason "…" [--lane name] [--delegated [--story ST
|
|
|
542
544
|
| `shell.restricted[]` | no | `{ pattern, lanes, why }`: only the lead and these lanes |
|
|
543
545
|
| `postEdit[]` | no | `{ files, exclude?, run }`: after each edit of a matching file. `{file}` is the file. Exit 127 (tool not installed) is skipped. |
|
|
544
546
|
| `tests[]` | no | Globs naming the test files, for the weakened-test and fix rules. Default: the usual conventions (`*.test.*`, `*.spec.*`, `__tests__/`, `test/`, `tests/`, `e2e/`, `*_test.go`, `test_*.py`). |
|
|
545
|
-
| `regression.prepare` | no | A command run in a fresh checkout before a fix's tests run there without the fix, such as `npm ci`.
|
|
547
|
+
| `regression.prepare` | no | A command run in a fresh checkout before a fix's tests run there without the fix, such as `npm ci`. The checkout's `node_modules` and virtualenvs are copied in first (a copy-on-write clone where the disk has one), so it can't change the checkout's own. |
|
|
546
548
|
| `checks[]` | no | `{ name, files, exclude?, run[], each?, owners?, ifMissing?, timeoutSeconds? }`: before finishing, when matching files changed. `each` runs the commands in every changed folder matching that glob. `owners` limits who may change the files (the lead always may). `ifMissing: "fail"` makes a missing tool an error (the default is to skip the check, which `verify` and a merge list as not run). `timeoutSeconds` (240 unless set) is how long each command may run; one that runs out of time leaves its branch at the head of the merge queue rather than sending it back. |
|
|
547
549
|
| `adapters` | no | `{ "<adapter>": false }` switches off an adapter that would otherwise be detected; `true` says the project wants that tool, so until it's set up here `next` gives its setup before any code. See [Adapters](#adapters). |
|
|
548
550
|
| `approvals.lead` | no | `true` lets the lead act on what the person says in chat, for when `!` isn't available (on a phone, say): it records their approvals with `code-kit approve`, and runs `shell.block` commands marked `person`. Default `false`. See [Approvals](#approvals). |
|