菜单
Run Google Test binaries in parallel using the gtest-parallel script. Use when needing to speed up test execution, run flaky tests with repeat, or filter specific tests.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Generate a professional HTML changelog from WebRTC git logs. Automatically categorizes changes, includes a high-level summary, and provides detailed commit and review links.
Provides commands for interacting with Gerrit CLs using git cl, including issue management and non-interactive uploads.
Automated code review following Harald Alvestrand's (hta@) standards for WebRTC. Use this skill to analyze CLs for thread safety, process hygiene, architectural robustness, and modern C++ adoption.
Automatically fix GN check errors in WebRTC BUILD.gn files. Use when encountering "Include not allowed", "rtc_source_set shall not contain cc files", or when needing to clean up non-absolute dependencies.
Runs the WebRTC include-cleaner tool (IWYU replacement) to fix headers in C++ files. Use when preparing a CL for upload, after modifying .cc or .h files, or when instructed to fix include regressions.
| name | gtest-parallel |
| description | Run Google Test binaries in parallel using the gtest-parallel script. Use when needing to speed up test execution, run flaky tests with repeat, or filter specific tests. |
gtest-parallel is a script that executes Google Test binaries in parallel,
providing speedup for single-threaded tests and tests that do not run at 100%
CPU.
The script is located at third_party/gtest-parallel/gtest-parallel.
Use --gtest_filter to run a select set of tests. It supports the same syntax
as Google Test (including exclusion with -).
third_party/gtest-parallel/gtest-parallel path/to/binary --gtest_filter=Foo.*:Bar.*
--timeout=TIMEOUT: Interrupt all remaining processes after the given time
(in seconds).--timeout_per_test=TIMEOUT_PER_TEST: Interrupt single processes after the
given time (in seconds).-d OUTPUT_DIR, --output_dir=OUTPUT_DIR: Output directory for test logs.
Logs will be available under gtest-parallel-logs/ inside the specified
directory.--dump_json_test_results=DUMP_JSON_TEST_RESULTS: Saves the results of the
tests as a JSON machine-readable file.Use --repeat=N to run tests multiple times.
third_party/gtest-parallel/gtest-parallel path/to/binary --repeat=1000
Use -w WORKERS or --workers=WORKERS to specify the number of parallel
workers (defaults to the number of cores).
Use --serialize_test_cases to run tests within the same test case sequentially
(useful if they share resources).