CI / Test Audit

Audits what is already in test/, .github/ and scripts/ci/. For writing a new test see write-sglang-test; for how the pipeline dispatches and gates work see ci-workflow-guide.

How to use it

Read action-items.md first. It is a catalog of patterns that have been applied to this repo, each with a way to spot it and example PRs. The catalog is the substance of this skill; everything below is only scaffolding.

The user says what to audit -- a test group, a stage, a workflow file, or a complaint like "this suite is slow" -- and how thoroughly. Read that scope and decide which patterns apply.

An audit is only useful if it is specific. "This suite could be trimmed" is not a finding; "TestFooLargePage is a strict subset of TestFooRetractLargePage, drop it" is. Every finding needs the file, the pattern it matches, and what to do.