Repository navigation
perf(security): write rollups and body fields without loading them into context - #1451
Merged
potiuk merged 1 commit intoSep 28, 2026
Merged
Conversation
…to context The optimize-skill out-of-context pass. Skills read the whole rollup comment or issue body into context to append one entry or change one field, and wrote it back with a hand-rolled PATCH. They now call the vetted-ops tracker procedures, so the rollup and the body never enter context, and the calls work under the secure setup. - rollup-append replaces the hand-built rollup posts and PATCH upserts in import, import-from-md, import-from-pr, invalidate, deduplicate, cve-allocate, issue-fix and sync. Entry templates keep their body text and drop the `<details>` envelope and marker line, which the tool writes. - rollup-amend-latest fills invalidate's draft id into the entry it just wrote. - rollup-fold replaces the read / wrap / PATCH / DELETE fold-legacy sequences (deduplicate, cve-allocate, issue-fix, sync). The legacy comment is deleted only after the append succeeded. - body-field-get / body-field-set replace whole-body fetches and rewrites that touched a single field (cve-allocate, issue-fix, sync). Sync keeps a whole-body write only where it adds sections the body lacks. - rollup-append and rollup-amend-latest (and github-rollup append / amend-latest) now print the rollup comment's URL, so invalidate's permalink and import-from-pr's recap do not need a second lookup. Each skill notes once how to run the same operations without the secure setup, through the github-rollup and github-body-field CLIs. The vetted-ops policy example grants each security caller exactly the operations it uses. Generated-by: Claude Code (Opus 5.5)
potiuk
force-pushed
the
perf/security-rollup-rewire
branch
from
September 28, 2026 09:49
c64f0ad to
ea4f3fa
Compare
This was referenced Sep 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on the P7 pre-filter PR; the last layer of the security family optimization (#1344). It is the optimize-skill out-of-context pass, built on the
vetted-op-trackerprocedures added two PRs below.Summary
Skills used to read the whole rollup comment or issue body into context to append one entry or change one field, then wrote it back with a hand-rolled PATCH. They now call the vetted-ops tracker procedures, so neither the rollup nor the body enters context. The calls also work under the secure setup, where
uv run … github-rollupcould not reachgh.rollup-appendrollup-amend-latestrollup-foldbody-field-get/body-field-set<details>envelope and marker line, which the tool writes.rollup-append/rollup-amend-latest, andgithub-rollup append/amend-latest, now print the rollup comment's URL on stdout. Invalidate's permalink and import-from-pr's recap use it instead of a second lookup.github-rollup/github-body-fieldCLIs.Test plan
prek run --all-files, including lychee;skill-and-tool-validate;check-placeholderscve-allocate/step-1/case-2is flaky on both sides (1/3 before, 2/3 after). It fails whenever the model lists thecve allocatedlabel as a second blocker.<details>line. They now describe it by the action label the tool writes into that line. Expected values are unchanged.Part of #1344.
Generated-by: Claude Code (Opus 5.5)
🤖 Generated with Claude Code