model-pr-history-knowledge

Query PR-driven model optimization history across SGLang, vLLM, TensorRT-LLM, and TokenSpeed.

783|67|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/BBuf/AI-Infra-Auto-Driven-SKILLS --skill model-pr-history-knowledge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: model-pr-history-knowledge
Source: https://github.com/BBuf/AI-Infra-Auto-Driven-SKILLS/tree/main/model-pr-optimization-history
Command: npx skills add https://github.com/BBuf/AI-Infra-Auto-Driven-SKILLS --skill model-pr-history-knowledge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

When optimizing or patching model serving paths, engineers often repeat work that upstream frameworks already solved or miss known regression risks. This Skill provides a queryable knowledge base of PR-driven model optimization histories so agents can ground patch planning, fast-path selection, and validation choices in inspected PR diffs rather than guesswork.

Core Features & Use Cases

  • Cross-framework PR history search: Query bilingual model-family history docs for SGLang, vLLM, TensorRT-LLM, and TokenSpeed using a local search helper with framework, model, language, and result-limit filters.
  • Actionable evidence extraction: Surface implementation files, symbols, prior fusions, quantization and MoE changes, validation lanes, and regression risks from per-PR diff audit cards.
  • SOTA loop integration: Feed history evidence into SGLang SOTA and Humanize optimization loops before patch planning, including competitor history when another framework is faster.
  • Use Case: Before writing a fused QK-norm patch for Qwen3.5 on SGLang, query the knowledge base to discover that vLLM and TensorRT-LLM already landed similar fusions, then cite the relevant PRs and source files in the run's analysis notes.

Quick Start

Ask the agent to look up prior PR optimization history for a model family, for example by running the query helper with a model slug and search terms before planning any serving patch.

Frequently Asked Questions about model-pr-history-knowledge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find prior optimization PRs for a model in SGLang or vLLM?

Run scripts/query.py from the skill directory with a framework and model slug, for example --framework sglang --model qwen3-core plus search terms. It prints matching history docs with paths and line-level snippets to read.

What frameworks does the model PR history knowledge base cover?

It covers four serving frameworks: SGLang, vLLM, TensorRT-LLM, and TokenSpeed. Model availability is framework-specific, so a family like MOSS-VL exists only in the SGLang index while Qwen3.5 appears across frameworks.

How do I search model history docs in Chinese or English?

Use the --lang option on scripts/query.py with en, zh, or both to select English docs, Chinese docs, or both. Each model family keeps bilingual README.en.md and README.zh.md files when practical.

When should I read competitor framework history before patching SGLang?

Read competitor history when vLLM, TensorRT-LLM, or TokenSpeed is the leading competitor or its trace suggests a missing SGLang fast path. This prevents assuming a gap is kernel-local when the competitor already landed a model-level fusion.

Are open PRs included in the merged model history cards?

No, open PRs are deliberately kept out of merged-history cards until their diffs are manually reviewed. The open-pr-watch.md file acts as a triage queue of pending PRs that may affect benchmark, profiler, and model-history guidance.

What are the limitations of the PR history knowledge base?

History docs can go stale as upstream frameworks merge new PRs, so dated PR Backfill Audit sections list recent merges not yet folded into the timeline. Always refresh live source and PRs for the exact target commit before patch planning.