skills.rest
guqiong96
guqiong96COMMUNITY
Explore all skills by this author →
GitHub

SGLang Bisect CI Regression

Automate SGLang CI regression debugging via temporal bisection and remote GPU reproduction.

105|9|Updated Feb 10, 2026
Search Tags:#debugging#troubleshooting#github actions#regression#bisect#ci
One-click install
npx skills add https://github.com/guqiong96/Lsglang --skill sglang-bisect-ci-regression-guqiong96
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: SGLang Bisect CI Regression
Source: https://github.com/guqiong96/Lsglang/tree/main/.claude/skills/sglang-bisect-ci-regression
Command: npx skills add https://github.com/guqiong96/Lsglang --skill sglang-bisect-ci-regression-guqiong96

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of identifying the root cause of consistently failing CI tests, whether it's due to a recent code change, hardware issues, or environmental factors.

Core Features & Use Cases

  • CI Log Analysis: Parses CI logs to pinpoint failure signatures and error messages.
  • Temporal Bisection: Identifies the exact commit or PR that introduced a regression by comparing passing and failing CI runs.
  • Hardware/Runner Analysis: Differentiates between code regressions and environment-specific issues by analyzing runner and hardware configurations.
  • Remote Reproduction: Optionally reproduces CI failures on a remote GPU server for deeper debugging.

Quick Start

Use the sglang-bisect-ci-regression skill to investigate the failing test 'test_lora_tp.py' and optionally reproduce it on user@host.

Frequently Asked Questions about SGLang Bisect CI Regression

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

FAQPage Schema
How do I find the exact commit that introduced a CI regression in SGLang?▼

To find a CI regression, this skill uses temporal bisection on scheduled CI runs to identify the exact commit or PR that introduced the failure. It automates root cause investigation for consistently failing tests.

Why does my GitHub Actions test fail only on specific runners?▼

Runner-specific test failures are diagnosed by analyzing runner-specific hardware and environment configurations. This helps differentiate between actual code regressions and environment-specific issues.

Can I reproduce CI failures on a remote GPU server?▼

Yes, you can reproduce CI failures on a remote GPU server. The skill optionally connects via SSH and uses Docker to recreate the failing environment for deeper debugging and troubleshooting.

How do I debug failing CI tests by parsing logs?▼

To debug failing CI tests, CI logs are parsed to pinpoint failure signatures and error messages. This isolates the root cause of the failure before performing temporal bisection on the runs.

Do I need SSH access to debug SGLang CI regressions?▼

You do not need SSH access to debug SGLang CI regressions. SSH access is only required if you choose to optionally reproduce the failures on a remote GPU server for deeper debugging.

Related Skills

Explore More Software Engineering Skills→
drunkcodingdrunkcoding
4

sglang-bisect-ci-regression

Bisect SGLang CI failures to identify regression-causing PRs or environment changes.

Community
Advanced
brainbrewlabsbrainbrewlabs
7

code-fixing

Fix code scanner, security auditor, and linter issues with verified edits and reports.

Official
Intermediate
kickinradkickinrad
3

install

Deploy a persona to a remote server as a Docker container with Tailscale SSH.

Community
Advanced
drndrn
23

bisect

Identify the Git commit that introduced a bug using git bisect.

Community
Advanced