You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
perf: cut the bodies of the most-invoked skills through progressive disclosure - part 2 of 2 #12244
I understand this as part 2 of 2 of #12240, split at intake. Its one done-when item is to measure the after figure the same way as the before figure: skill body bytes, weighted by invocations over a comparable window. That measurement depends on the body cuts in part 1 (#12243) landing first, so I listed #12243 as a blocker. The issue doesn't name the before baseline or the window. The parent issue #12240 should say where they come from.
Activity
github-actions commentedon Nov 2, 2026
Proposed work class: work-class: read-only
Basis: automated intake triage; the lanes App applied this class.
Size: Small
Complexity: Low
Uncertainty: Knowable
Flags: none
Blocked by: #12243
I understand this as part 2 of 2 of #12240, split at intake. Its one done-when item is to measure the after figure the same way as the before figure: skill body bytes, weighted by invocations over a comparable window. That measurement depends on the body cuts in part 1 (#12243) landing first, so I listed #12243 as a blocker. The issue doesn't name the before baseline or the window. The parent issue #12240 should say where they come from.
Automated triage, applied by the lanes App.
melodic-automation-lanes commentedon Nov 2, 2026
Not admitted to the issue lane yet: blocker #12243 is not closed by a listed human or a merge.