potiuk opened a new pull request, #410:
URL: https://github.com/apache/airflow-steward/pull/410

   ## Summary
   
   Profiling a 12-tracker bulk sync showed every subagent loading the full 
**3425-line SKILL.md (~30K tokens)** regardless of which step it was running. 
Extract the four heaviest sections into focused subdocs so subagents can load 
just the slice they need.
   
   ## Structure
   
   ```
   .claude/skills/security-issue-sync/
   ├── SKILL.md                  658 lines  (overview + dispatcher + Step 
0/2a/2c/3/6 inline)
   ├── bulk-mode.md              247 lines  (orchestration contract)
   ├── gather.md                 775 lines  (Step 1 sub-steps 1a-1h)
   ├── signals-to-actions.md   1088 lines  (Step 2b lookup table)
   └── apply-and-push.md         768 lines  (Step 4 + Step 5/5a/5b/5c)
   ```
   
   ## Subagent loading savings
   
   | Subagent role | Before | After | Reduction |
   |---|---|---|---|
   | Gather-only (Step 1) | 3425 lines | 1412 lines | **59%** |
   | Bulk orchestrator | 3425 lines | 884 lines | **74%** |
   | Apply orchestrator | 3425 lines | 1405 lines | **59%** |
   | Step 2b proposal builder | 3425 lines | 1725 lines | **50%** |
   
   ## Notes for reviewers
   
   - **No behavior change** — pure file restructure. Same pattern 
\`setup-steward\` already uses (\`adopt.md\` / \`upgrade.md\` / \`verify.md\` 
alongside \`SKILL.md\`).
   - Cross-references rewritten to point at the new subdoc files; same-file 
anchors preserved.
   - Injection-guard callout (Pattern 4) intentionally **duplicated** in 
\`SKILL.md\` + \`gather.md\` so subagents that only load gather.md still see 
the guard.
   - \`skill-and-tool-validator\` passes after the extraction.
   
   ## Test plan
   
   - [x] \`skill-and-tool-validator\` clean run
   - [x] \`markdownlint\` clean run
   - [ ] Next bulk sync run on \`airflow-s/airflow-s\` confirms subagents load 
the smaller slice
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to