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

devtools-verification

GitHub

提供项目构建、测试及代码健康检查的规范指令。指导如何运行特定文件或目录的测试，执行编译和Lint检查，并强调在提交前运行验证的最佳实践，确保代码质量与合规性。

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

Trigger Scenarios

需要构建项目时需要运行测试用例时需要检查代码规范或Lint错误时执行自动化构建命令前

Install

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

More Options

Non-standard path

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

Use without installing

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

指定 Agent (Claude Code)

npx skills add ChromeDevTools/devtools-frontend --skill devtools-verification -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-verification",
    "description": "MANDATORY: Activate this skill ANY TIME you need to build the project, run tests, or verify code health in DevTools. You MUST use this skill before executing commands like npm test, npm run build, autoninja, or linters, as it contains critical, repository-specific instructions on how to correctly format these commands, filter test runs, and interpret failures."
}

Instructions on how to verify your changes

Testing

To test a file, you can run npm run test -- <FILEPATH> where FILEPATH is a path to a *.test.ts file, relative to the working directory.
Test files are usually defined alongside their implementation. So if you are working on front_end/panels/timeline/TimelinePanel.ts, you would expect the test file to be defined in front_end/panels/timeline/TimelinePanel.test.ts.
You can also test an entire directory. For example, npm run test -- front_end/models/trace will run all tests in that directory.

Building & compiling

Check for build issues by running autoninja -C out/Default.

Linting

npm run lint will execute ESLint and StyleLint. It will report any violations and automatically fix them where possible.
To run the linter on a specific file or directory, you can run npm run lint -- <PATH> where PATH is a path to a file or directory. This will also automatically fix violations where possible.