Repository navigation
perf(source-control): move the worktree nesting measurement out of the skill hub - #12387
Conversation
…e skill hub The /source-control:worktree body drops from 39,059 to 32,469 bytes. The nesting invariant's dated measurement moves to reference/nesting-invariant.md, which the SSOT test now treats as the owner, and every pointer follows it. The quoted isolation-enforcement passage becomes our rules plus a docs pointer with an as-of date and recheck trigger. Refs: #12243 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
claude-review reviewed Code review: PR #12387, incremental (a70cc90 → 68eba76)No new findings. I read every hunk of the incremental diff in all 4 files in scope. Both earlier findings are fixed
Regression check on the SSOT testI read
Other checks
|
|
claude-security-review reviewed Security review: PR #12387 (incremental since a70cc90), no security issues foundI read every hunk in What changed since the last review
Instruction-surface lens. The nesting-invariant edits are a skill reference body, so I checked each change by its consequence:
I recognised removals by their consequence and did not read the instruction exception register for this pass. Trust controls. Nothing in this change touches:
PR context. The description matches the change. It contains no embedded instructions aimed at the review lane. Prior findings. This lane's only earlier post is the clean summary for a70cc90, with no findings to repeat. This is round 0 of 3, so the cap does not apply. critical-findings: 0 |
…ference Addresses the claude-review findings on a70cc90. Three remaining citations still named skills/worktree/SKILL.md as the owner of the nesting invariant: the worktree-create.sh --root help text, the same script's comment (which also used the old heading name) and the worktree-root convention. They now name the reference file, along with the README's second mention. The reference file stops quoting the hooks page and stops restating issue #16600's state. It keeps our exec-form rule, plus a pointer with its section anchor, an as-of date and a recheck trigger. Refs: #12243 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Reply to the claude-review summary on
Fixed in 68eba76. A sweep for the same owner phrasing found two more sites, and both are fixed too: the README's second mention (line 489), and the comment at |
Refs: #12243
Summary
First of the six body cuts #12243 asks for. The
/source-control:worktreeSKILL.md goes from 39,059 to 32,516 bytes (about 17% less loaded per invocation). Its action routing, safety invariants and gates stay in the hub.Fix
skills/worktree/reference/nesting-invariant.md, which is read on demand. The hub keeps a short pointer section under the same heading.nesting-invariant-ssot.test.shnow names the reference file as the owner. Every pointer site follows it: SKILL.md,context/create.md,fixtures/README.md, the probe script, both hooks,worktree-create.shand the plugin README..claude/rules/skill-bodies-state-current-rules.md.Verification
/docs-hygiene:compress compare(freshcompare-labeler, before against after): VERDICT PASS, with no SEMANTIC LOSS. It raised two AMBIGUITY rows, and both are fixed on this head: PowerShell's scope is restored to "the git-redirect or command-shape check", and the reference file now says itsfixtures/paths are relative to the skill directory.scripts/check-affected.sh --testson the committed head: 14 passed, 2 skipped. That includesnesting-invariant-ssot.test.sh(22 cases, 0 failures).claude plugin eval <copy> --case 'worktree-*' --ablation none --runs 2 -j 2 --scaffold --allow-tools Bash Write Edit --model claude-opus-5-5.run-validity.py --runs 2 --scaffolded(after fix(evals): check case helper plugins per case and excuse plugin-data compound denials #12388) marks round 1 VALID on both arms.lscalls denied under the run's own plugin-data directory. The gate does not count these.Readof the sandboxsettings.jsonwas denied.settings.jsondenial, plus one unfiredSkillcall inworktree-not-pr-lifecycle.worktree-create-routes-through-helper: its 0.25 run under that denial hit each version once.audit, whose text this cut left unchanged.Remaining on #12243
The other five cuts are not started:
/source-control:pull-request,/session-flow:handoff,/discovery:research,/evals:plugin-evaland/source-control:commit. Each needs its own paired before and after eval run on a host.Related
🤖 Generated with Claude Code