BBuf/model-pr-diff-dossier
skills/model-optimization/model-pr-diff-dossier/SKILL.md
Use when creating or revising model PR optimization history documents for SGLang, vLLM, or another serving framework that cite GitHub PRs. Requires manual, per-PR source-diff review and documentation of motivation, key implementation approach, most important code excerpts, reviewed files, and validation implications instead of generated or one-line summaries.
$ install --global
skillsauthnpx skillsauth add BBuf/AI-Infra-Auto-Driven-SKILLS model-pr-diff-dossierInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 17, 2026, 2:23 AM113.4s2 files scanned
SKILL.md
- name:
- model-pr-diff-dossier
- description:
- Use when creating or revising model PR optimization history documents for SGLang, vLLM, or another serving framework that cite GitHub PRs. Requires manual, per-PR source-diff review and documentation of motivation, key implementation approach, most important code excerpts, reviewed files, and validation implications instead of generated or one-line summaries.
Model PR Diff Dossier
Use this skill before publishing any model PR optimization history document that cites framework PRs.
Non-Negotiable Standard
Do not summarize a PR with only a title-level sentence. Do not use a script or bulk generator to fill motivation, implementation notes, or code excerpts.
For every PR cited as model optimization evidence, the document must include or link to a diff-reviewed PR card with:
- PR link, title, state, merge time when available, additions/deletions, and changed-file count.
- Motivation: why the PR existed, inferred from PR body, title, issue context, docs changes, tests, and code diff.
- Key implementation idea: what runtime path changed and how the patch implements the change.
- Key code excerpts: short, relevant snippets from the actual diff, not invented pseudocode.
- Reviewed files: important files from the full diff, grouped by runtime/docs/tests where possible.
- Validation implications: tests, benchmark paths, launch flags, or regression lanes implied by the diff.
- Diff coverage note: state that the full diff was fetched/read and include diff line count.
Workflow
- Collect exact PR links from the target model history files. Use GitHub PR URLs, not bare
#123text. - Open each PR diff directly with GitHub,
gh pr diff, or the local framework repository commit. Read the changed source files, not just the PR title. - For merged PRs, cross-check the final mainline code in the relevant framework checkout when the diff is ambiguous.
- Write the PR card manually in the matching model history document. Use
references/card-schema.mdwhen you need the exact card shape. The card must name concrete files/functions/classes and include a short real code excerpt. - For docs-only or config-only PRs, quote the exact command/config line that changed and explain why it matters for serving or validation.
- After each model family, review the cards for repeated shallow words such as "follow-up", "bugfix", or "optimization"; replace them with concrete implementation detail.
- Run repository tests and formatting before publishing.
Review Gate
A model PR history is not ready if any PR card says only "follow-up", "bugfix", "docs", or "optimization" without:
- named files/functions/classes touched by the diff,
- a concrete motivation,
- a concrete implementation summary,
- and at least one code excerpt or an explicit reason why the PR is docs-only.
Related Skills
BBuf/vllm-sota-humanize-loop
development
VerifiedTrustedCommunity
Run an autonomous Humanize-governed vLLM SOTA performance loop for one LLM model: first perform the fixed fair vLLM/SGLang/TensorRT-LLM deployment search and benchmark, then start one RLCR loop that repeatedly decides the gap, profiles the current bottleneck, runs layer/kernel pipeline analysis, patches vLLM code, optionally uses ncu-report-skill for kernel evidence, and revalidates until vLLM matches or beats the best observed framework under the same workload and SLA.
423SKILL.mdUpdated May 27, 2026
BBuf/llm-pipeline-analysis
devops
VerifiedTrustedCommunity
Inspect LLM torch profiler traces at forward-pass, layer, and kernel level. Use when you need layer timings, anchor-kernel boundaries, representative kernel flows, or Perfetto time ranges.
423SKILL.mdUpdated May 21, 2026
BBuf/sglang-sota-humanize-loop
development
VerifiedTrustedCommunity
Run an autonomous Humanize-governed SGLang SOTA performance loop for one LLM model: first perform the fixed fair SGLang/vLLM/TensorRT-LLM deployment search and benchmark, then start one RLCR loop that repeatedly decides the gap, profiles the current bottleneck, runs layer/kernel pipeline analysis, patches SGLang code, optionally uses ncu-report-skill for kernel evidence, and revalidates until SGLang matches or beats the best observed framework under the same workload and SLA.
423SKILL.mdUpdated May 17, 2026
BBuf/model-pr-history-knowledge
documentation
VerifiedTrustedCommunity
Use when an SGLang, vLLM, or TensorRT-LLM serving/model optimization task needs prior model-family PR evidence. Query and read the PR-driven history docs under model-pr-optimization-history before choosing source paths, fast paths, kernel/fusion ideas, regression risks, or validation lanes.
423SKILL.mdUpdated May 17, 2026