Agent Skills › ChromeDevTools/devtools-frontend › devtools-ci

devtools-ci

GitHub

用于分析 Chromium/DevTools LUCI 构建结果和 trybot 失败，包括检查构建状态、编译错误及详细测试回归。

.agents/skills/devtools-ci/SKILL.md ChromeDevTools/devtools-frontend

Trigger Scenarios

分析构建失败原因排查测试回归问题

Install

npx skills add ChromeDevTools/devtools-frontend --skill devtools-ci -g -y

More Options

Non-standard path

npx skills add https://github.com/ChromeDevTools/devtools-frontend/tree/main/.agents/skills/devtools-ci -g -y

Use without installing

npx skills use ChromeDevTools/devtools-frontend@devtools-ci

指定 Agent (Claude Code)

npx skills add ChromeDevTools/devtools-frontend --skill devtools-ci -a claude-code -g -y

安装 repo 全部 skill

npx skills add ChromeDevTools/devtools-frontend --all -g -y

预览 repo 内 skill

npx skills add ChromeDevTools/devtools-frontend --list

SKILL.md

Frontmatter

{
    "name": "devtools-ci",
    "description": "Triage and analyze Chromium\/DevTools LUCI build results and trybot failures, including high-level builder status, compile errors, and detailed test failures. Use this to inspect trybot buildbucket (bb) results for a patchset overview or to query ResultDB directly for comprehensive, actionable information about specific test regressions and infrastructure issues."
}

LUCI Build Triage & Analysis

This skill provides access to specialized triage tools maintained within the depot_tools repository. These tools are used to inspect Buildbucket results and ResultDB test failures.

Environment & Auth Discovery

Environment: Always execute these scripts using vpython3 instead of python3 to ensure all hermetic dependencies (like httplib2) are satisfied.
Authentication: Use bb auth-info to proactively check if you are logged into Buildbucket. If not, inform the user they must run bb auth-login.

Locating the Tools

The triage scripts and their detailed documentation are located relative to the depot_tools installation:

Locate Depot Tools: Run which gerrit_client.py to find your local depot_tools root.
Navigation:
- Buildbucket (bb_wrapper.py): Found in <DEPOT_TOOLS_ROOT>/agents/skills/buildbucket/
  - Strengths: High-level Build info (is it failing? what steps failed?), compile errors, and infra issues.
- Test Results (luci_triage.py): Found in <DEPOT_TOOLS_ROOT>/agents/skills/luci-test-results/
  - Strengths: Detailed Test info (specific test case failures in ResultDB).

Troubleshooting

"No Artifacts Found": This usually occurs if:
1. The build failed so early (e.g., bot setup) that no artifacts were produced.
2. The build is too old and logs have been purged.
3. There is an authentication issue.
- Fallback: Try bb log <build_id> <step_name> to see the raw output for the failed step.

Available Skills in Depot Tools

Once you have located the depot_tools directory, read the following files to understand how to use each tool:

buildbucket: Used for high-level builder status and compile failures.
- Read: <DEPOT_TOOLS_ROOT>/agents/skills/buildbucket/SKILL.md
luci-test-results: Used for detailed ResultDB test failure analysis.
- Read: <DEPOT_TOOLS_ROOT>/agents/skills/luci-test-results/SKILL.md

Usage at Runtime

When you need to triage a build:

Locate depot_tools as described above.
Read the relevant SKILL.md file from depot_tools.
Follow the instructions in that file to execute the Python scripts (e.g., bb_wrapper.py or luci_triage.py) using their absolute paths.