sglang-humanize-review

Review SGLang pull requests against a corpus of historical human maintainer review discussions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Generic AI code review misses the specific correctness, GPU runtime, API compatibility, and testing concerns that SGLang maintainers actually raise, producing feedback that does not match how the project is really reviewed.

Core Features & Use Cases

  • Corpus-grounded review: Consults a gzip JSONL corpus of 40,110 review threads and 93,774 human comments from sgl-project/sglang PRs (project start through 2026-07-27), covering inline review threads, PR conversations, and review submissions with original multilingual text preserved.
  • Exhaustive sweep and synthesis: A mandatory segmented sweep script aggregates every relevant historical thread by touched path and risk keyword, then a first-N query tool supports follow-up drill-downs by category, reviewer, kind, or PR number.
  • Structured review output: Every review opens with a PR comprehension block (change summary plus Mermaid execution flowchart with changed nodes marked), followed by a historical synthesis, severity-ordered findings with file/line references, and test or benchmark gaps.
  • Use Case: Before opening a PR that touches the SGLang scheduler and CUDA graph runner, run the sweep with those paths and keywords like "cuda graph" to surface recurring maintainer concerns, then produce a review-prep pass listing likely reviewer objections and missing benchmark evidence.

Quick Start

Review my current SGLang diff the way a human maintainer would, grounding the findings in the historical review corpus.

Frequently Asked Questions about sglang-humanize-review

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

FAQPage Schema
How do I review a SGLang PR like a human maintainer?

Inspect the diff first, then run the summarize script with every touched path and risk keywords to exhaustively sweep the review corpus. Write a short synthesis of recurring maintainer opinions, produce a Mermaid comprehension diagram, and list findings ordered by severity with file and line references.

What data does the SGLang review corpus contain?

The corpus holds 40,110 threads and 93,774 human comments from sgl-project/sglang PRs through 2026-07-27, including inline review threads with diff hunks, top-level PR conversations, and review submissions. Bot and coding-agent authored content is excluded, and original comment languages are preserved.

Can I query the review corpus by file path or reviewer?

Yes, the query script supports filters for path substring, category, thread kind, PR number, and reviewer login, with markdown or JSONL output. Use it for follow-up drill-downs after the mandatory exhaustive sweep, not as the primary review evidence source.

Does the corpus cover SGLang PRs after July 2026?

No, the bundled gzip corpus ends at 2026-07-27, so reviews after that date must be read live from GitHub. You can regenerate the corpus with the collector script by bumping the end-year parameter when a refresh is requested.

Why must review findings be verified against the PR branch?

Claims about call-site coverage, method shadowing, or exact line numbers are base-sensitive, and a stale local checkout produces confident false positives. Verify with gh pr diff, the GitHub contents API at the PR SHA, or git show, and label unverifiable findings as needing branch verification.