open/repo-standard
1
0
Fork 0
Code Issues Releases 7 Activity

fix(engine): print engine version, so a stale plugin cache is visible

Browse source 
Measured 2026-08-04: two repos (llm-security, config-audit) independently
proved the /repo-standard skill had resolved ${CLAUDE_PLUGIN_ROOT} to a
cached 0.1.1 while 0.2.0 was installed and the catalog pinned it — same
instruction, same variable, wrong engine. 0.1.1 has neither BADGE-COUNT nor
README-LANGUAGE, so a broadcast recommending the skill produced clean-looking
runs that could not have found what they were sent to find.

The header line and --json output now carry `repo-standard v<version>`
(headerLine/withEngineVersion, both pure and unit tested). SKILL.md tells the
reader to confirm it against the catalog pin before trusting green. The
stale-cache resolution itself is the harness's, not this repo's — not fixed
here, only made visible instead of silent.

TDD: 4 new tests. 111/111 green.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01496ZWasKPnA627crFBXWhe
This commit is contained in:
Kjell Tore Guttormsen 2026-08-04 13:12:29 +02:00
commit f85b9d3229
7 changed files with 88 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

17
skills/repo-standard/SKILL.md
View file

@ -12,7 +12,7 @@ description: >-
"fiks install-blokka", "finn døde repo-referanser", "gjør repoet presentabelt".
Trigger when someone is about to release, publish, or hand over a repository
and wants its public surface to hold up.
version: "0.2.1"
version: "0.2.2"
---
# repo-standard — the per-repo gate
@ -26,14 +26,25 @@ the script cannot encode.
node "${CLAUDE_PLUGIN_ROOT}/scripts/repo-standard-check.mjs" --dir "$PWD"
Findings are `ERROR` (blocks), `WARN` (look, then decide), `SKIP` (the check
could not run), `OK`. Exit 1 on any ERROR. Add `--offline` to skip the one
network call, `--json` for machine output, `--refresh` to compare the bundled
could not run), `OK`. Exit 1 on any ERROR. Add `--offline` to skip the two
network calls, `--json` for machine output, `--refresh` to compare the bundled
register against the live org listing.
**Never report a `SKIP` as a pass.** A SKIP means the gate could not see enough
to judge — an unreachable forge, an untagged repo, a link leaving the
repository. Say which.
**Confirm the version before you trust a green run.** Measured 2026-08-04:
`${CLAUDE_PLUGIN_ROOT}` resolved to a cached `0.1.1` in a live session while
`0.2.0` was installed and the catalog pinned it — same instruction, same
variable, wrong engine, and nothing in the output said so at the time. Two
repos proved it by running both versions against the same checkout: `0.1.1`
resurrected three findings `0.1.2`/`0.1.3` had already fixed. The header line
and `--json` output now both carry `repo-standard v<version>` — read it, and
if it does not match what the catalog pins (`ktg-plugin-marketplace`'s
`marketplace.json`, or ask the operator), say so instead of reporting the run
as clean.
**Report in buckets, not in a flat list.** Every finding also carries `broken`
(a stranger is blocked or misled), `missing` (an expected artefact is absent) or
`weakening` (present, but reads as amateur). That is the order the work actually