docks-kit 0.25.0 → 0.26.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/AGENTS.md +6 -6
- package/README.md +29 -9
- package/cli/dist/docks-kit.js +24688 -0
- package/cli/docs/command-guards.md +1 -1
- package/cli/docs/install.md +26 -6
- package/cli/docs/omp-context.md +1 -1
- package/cli/docs/omp-models.md +1 -1
- package/cli/src/agentDocs/agentFirstCheck.ts +786 -0
- package/cli/src/agentDocs/bridgeCheck.ts +226 -0
- package/cli/src/agentDocs/commands.ts +63 -0
- package/cli/src/agentDocs/prTemplate.ts +211 -0
- package/cli/src/agentDocs/services.ts +202 -0
- package/cli/src/agentDocs/shared.ts +730 -0
- package/cli/src/agentDocs/verifySkill.ts +136 -0
- package/cli/src/argv.ts +25 -1
- package/cli/src/commands/agentDocs.ts +29 -0
- package/cli/src/commands/plan.ts +29 -0
- package/cli/src/commands/skill.ts +29 -0
- package/cli/src/commands/update.ts +87 -28
- package/cli/src/generated/sotPayload.ts +50 -78
- package/cli/src/main.ts +12 -3
- package/cli/src/plan/bytes.ts +110 -0
- package/cli/src/plan/checkout.ts +341 -0
- package/cli/src/plan/commands.ts +1192 -0
- package/cli/src/plan/github.ts +816 -0
- package/cli/src/plan/records.ts +623 -0
- package/cli/src/plan/repository.ts +53 -0
- package/cli/src/plan/reviews.ts +292 -0
- package/cli/src/plan/services.ts +256 -0
- package/cli/src/plan/types.ts +164 -0
- package/cli/src/skills/commands.ts +142 -0
- package/cli/src/skills/config.json +30 -0
- package/cli/src/skills/files.ts +74 -0
- package/cli/src/skills/frontmatter.ts +148 -0
- package/cli/src/skills/guard.ts +366 -0
- package/cli/src/skills/kitGate.ts +406 -0
- package/cli/src/skills/rubric.ts +143 -0
- package/package.json +7 -4
package/AGENTS.md
CHANGED
|
@@ -32,9 +32,9 @@ Per-folder conventions live in nested `AGENTS.md` nodes. An agent can load only
|
|
|
32
32
|
| `SoT/toolchain.json` | Toolchain floors manifest (verified pins consumed by EngineNative; optional `upstream` source read by `docks-kit toolchain outdated`) |
|
|
33
33
|
| `SoT/.omp/` | Kit-owned omp SoT: `AGENTS.md`, `config.yml`, `models.yml`, `mcp.json`, `intercom.json`, and the kit plugin source `plugin/` |
|
|
34
34
|
| `install.sh` / `install.ps1` | POSIX and Windows global installers. Each installer stops on a host outside the support matrix before it downloads anything. |
|
|
35
|
-
| `.github/workflows/release-cli.yml` | `cli-v*` release: four binaries (Linux x64 and arm64, macOS arm64, Windows x64), plus `SHA256SUMS` and npm publish |
|
|
35
|
+
| `.github/workflows/release-cli.yml` | `cli-v*` release: four binaries (Linux x64 and arm64, macOS arm64, Windows x64), plus `SHA256SUMS`, the bundle's source map `docks-kit.js.map`, and npm publish |
|
|
36
36
|
| `README.md` | Front door |
|
|
37
|
-
| `package.json` / `bun.lock` | npm package: `bin` = `cli/
|
|
37
|
+
| `package.json` / `bun.lock` | npm package: `bin` = `cli/dist/docks-kit.js`, a minified bundle of the CLI and the generated in-memory SoT payload that `prepack` builds (`bun run build:bundle`); `cli/src` ships too, for the checkout launchers |
|
|
38
38
|
| `docs/PLAN.md` | Plan pointer and project plan rules. The plan record is a GitHub issue; no plan markdown is tracked. `docs/AGENTS.md` routes to it. |
|
|
39
39
|
| `AGENTS.md` | This file — tool-agnostic instructions |
|
|
40
40
|
|
|
@@ -87,8 +87,8 @@ Project-skill authoring rules (scope, canonical layout, vendored `unslop`, citat
|
|
|
87
87
|
|
|
88
88
|
## Kit plugin content
|
|
89
89
|
|
|
90
|
-
`SoT/.omp/plugin/` holds skills at `skills/<name>/SKILL.md`, task agents at `agents/<name>.md`, and the extensions that `package.json` `omp.extensions` names. It ships the 32 docks and plan-lifecycle skills, the `workspace-hygiene` skill, the `code-reviewer` and `plan-reviewer` agents, the `hygiene`, `verify-gate`, and `context-tree-nudge` extensions, the trigger rules in `rules/`, and the `/cleanup` command. A skill reports a problem in DocksDocks/
|
|
91
|
-
After a skill edit, run `bun cli/scripts/skill-content-hash.ts --write` to refresh its `metadata.content_hash` and `metadata.updated`; `--check` names each stale skill. The
|
|
90
|
+
`SoT/.omp/plugin/` holds skills at `skills/<name>/SKILL.md`, task agents at `agents/<name>.md`, and the extensions that `package.json` `omp.extensions` names. It ships the 32 docks and plan-lifecycle skills, the `workspace-hygiene` skill, the `code-reviewer` and `plan-reviewer` agents, the `hygiene`, `verify-gate`, and `context-tree-nudge` extensions, the trigger rules in `rules/`, and the `/cleanup` command. A skill reports a problem in DocksDocks/docks-kit. `bun run check` checks this content with four tests in `cli/test/unit/plugin/`: `skills.test.ts` (layout and name, frontmatter, report section, shared copies, references, durable anchors, transform guard, trigger collisions, score floor), `contentHash.test.ts`, `agents.test.ts` (agent rules, score floor), and `extensions.test.ts` (each entry imports and has a default function export).
|
|
91
|
+
After a skill edit, run `bun cli/scripts/skill-content-hash.ts --write` to refresh its `metadata.content_hash` and `metadata.updated`; `--check` names each stale skill. The skill checks, the 16-point rubric, and the check data in `config.json` (floors, report section, shared-copy groups, transform list) are in `cli/src/skills/`, which `docks-kit skill guard` and `docks-kit skill score` also use; the agent, reference, trigger, extension, and content-hash checks are in `cli/scripts/pluginContent/`.
|
|
92
92
|
|
|
93
93
|
## Plans
|
|
94
94
|
|
|
@@ -102,8 +102,8 @@ Per the agents.md open standard, place an `AGENTS.md` inside any subdirectory th
|
|
|
102
102
|
|
|
103
103
|
```bash
|
|
104
104
|
# Clone and sync the kit
|
|
105
|
-
git clone <this-repo> ~/projects/
|
|
106
|
-
cd ~/projects/
|
|
105
|
+
git clone <this-repo> ~/projects/docks-kit
|
|
106
|
+
cd ~/projects/docks-kit
|
|
107
107
|
./docks-kit sync --dry-run # preview before applying
|
|
108
108
|
./docks-kit sync # deploy the omp SoT (additive)
|
|
109
109
|
./docks-kit toolchain check # verify installed tools against SoT/toolchain.json floors
|
package/README.md
CHANGED
|
@@ -11,8 +11,8 @@ Supported harness: **Oh My Pi (`omp`)**.
|
|
|
11
11
|
## Quick start
|
|
12
12
|
|
|
13
13
|
```bash
|
|
14
|
-
git clone https://github.com/DocksDocks/
|
|
15
|
-
cd ~/projects/
|
|
14
|
+
git clone https://github.com/DocksDocks/docks-kit.git ~/projects/docks-kit
|
|
15
|
+
cd ~/projects/docks-kit
|
|
16
16
|
./docks-kit sync # deploy the omp SoT
|
|
17
17
|
./docks-kit sync --dry-run # preview the sync without a write
|
|
18
18
|
./docks-kit toolchain # doctor view: verified-version floors for external tools
|
|
@@ -40,6 +40,23 @@ upstream installer when Bun is absent: by the POSIX launcher and installer, and
|
|
|
40
40
|
by sync's Bun bootstrap, which a release binary can also run. The Windows
|
|
41
41
|
launcher and installer use Invoke-WebRequest.
|
|
42
42
|
|
|
43
|
+
### Move a checkout of DocksDocks/public
|
|
44
|
+
|
|
45
|
+
The kit moved from DocksDocks/public to DocksDocks/docks-kit. To move a
|
|
46
|
+
checkout of DocksDocks/public, run these commands from the checkout's root:
|
|
47
|
+
|
|
48
|
+
```
|
|
49
|
+
git remote set-url origin https://github.com/DocksDocks/docks-kit.git
|
|
50
|
+
./docks-kit update # Linux and macOS
|
|
51
|
+
.\docks-kit.ps1 update # Windows
|
|
52
|
+
./docks-kit sync # Linux and macOS
|
|
53
|
+
.\docks-kit.ps1 sync # Windows
|
|
54
|
+
```
|
|
55
|
+
|
|
56
|
+
The update pulls from DocksDocks/docks-kit. The sync then deploys the skills
|
|
57
|
+
with their new report target: a launcher that runs a fresh compiled binary
|
|
58
|
+
skips the sync that the update chains. A global npm install needs nothing.
|
|
59
|
+
|
|
43
60
|
## CLI
|
|
44
61
|
|
|
45
62
|
```text
|
|
@@ -125,7 +142,7 @@ marketplace when no uninstall failed and it can read the marketplace registry.
|
|
|
125
142
|
It only warns about a project-scope install, with the manual command. When a
|
|
126
143
|
read fails, sync warns and skips that step, and a later sync tries again.
|
|
127
144
|
Report a problem with a skill, an agent, or the kit in
|
|
128
|
-
[DocksDocks/
|
|
145
|
+
[DocksDocks/docks-kit](https://github.com/DocksDocks/docks-kit/issues).
|
|
129
146
|
|
|
130
147
|
## Repository map
|
|
131
148
|
|
|
@@ -156,13 +173,16 @@ Details: `docks-kit docs platforms`.
|
|
|
156
173
|
|
|
157
174
|
Tagging `cli-v*` builds four standalone binaries: `docks-kit-linux-x64`,
|
|
158
175
|
`docks-kit-linux-arm64`, `docks-kit-darwin-arm64`, and
|
|
159
|
-
`docks-kit-windows-x64.exe`. The workflow attaches them plus `SHA256SUMS`
|
|
160
|
-
|
|
161
|
-
with OIDC provenance.
|
|
176
|
+
`docks-kit-windows-x64.exe`. The workflow attaches them plus `SHA256SUMS` and the
|
|
177
|
+
bundle's source map `docks-kit.js.map` to the GitHub release. npm publishes the
|
|
178
|
+
exact package tarball through trusted publishing with OIDC provenance.
|
|
162
179
|
Published binaries, checksums, and release notes are available on
|
|
163
|
-
[GitHub Releases](https://github.com/DocksDocks/
|
|
164
|
-
Each `docks-kit` npm release
|
|
165
|
-
|
|
180
|
+
[GitHub Releases](https://github.com/DocksDocks/docks-kit/releases).
|
|
181
|
+
Each `docks-kit` npm release runs one minified JavaScript bundle of the CLI and
|
|
182
|
+
its generated payload (`cli/dist/docks-kit.js`), so releases are versioned config
|
|
183
|
+
snapshots without shipping the authoring `SoT/` tree. The package does not ship
|
|
184
|
+
the source map; the bundle's last line `//# debugId=<hex>` matches the map of
|
|
185
|
+
the same release.
|
|
166
186
|
|
|
167
187
|
## Deeper docs
|
|
168
188
|
|