Guides the initial analysis and impact assessment of a V8 security report, strictly excluding implementation or fixing.
Manages git task isolation and environment setup in V8. Use at the start of any new task or bug fix. Do not use for general C++ editing.
Runs a parallel multi-subagent V8 code review covering security, V8 Sandbox safety, GC invariants, compiler/codegen logic, concurrency, performance, tests, and style, then verifies and merges the findings. Use when reviewing a V8 CL, commit, or local diff. Do…
Executes and interprets V8 tests. Use when running unittests, cctest, or mjsunit, or when debugging test failures. Do not use for building.
Runs and reports the checks that a change to experimental/redline must pass before upload. The checks cover formatting, lint, the build, the selftests, the parser round trip and the golden traces. They also cover the Markdown links, the ASD-STE100 language of…
Manages the V8 feature shipping lifecycle, including checking feature status and consistency in src/flags/feature-flags.h, advancing features through shipping steps (experimental, pre-stage, stage, ship), checking Finch studies, fieldtrial configs, Origin…
Workflow for issue-based debugging in V8. Use when tasked with debugging a specific issue, usually associated with a Buganizer ID or a specific reproduction script. Do not use for performance regressions.
Workflow for automatically fixing errors or addressing comments on a Gerrit CL requested by the user.