Menu
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.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Managing and querying Perfetto traces using the trace_processor MCP server.
Documentation for conditional testing in V8 using gm.py.
Guides the initial analysis and impact assessment of a V8 security report, strictly excluding implementation or fixing.
Executes and interprets V8 tests. Use when running unittests, cctest, or mjsunit, or when debugging test failures. Do not use for building.
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 general debugging tasks without the overhead of issue tracking. Use when investigating crashes, hangs, or unexpected behavior where no specific issue ID is provided. Do not use when issue ID is provided.
| name | v8-workflow |
| description | 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. |
This skill defines the standard process for setting up and managing your development environment in V8.
Before starting any feature or bug fix, you MUST decide on a strategy:
Isolated Strategy (Recommended): Create a dedicated git worktree and
branch. This prevents cross-contamination between tasks. Use
create_worktree.sh.
Reuse Strategy: Work in the current directory and branch.
Issue Reset: If starting a new task without a worktree, always ask
before resetting the git cl issue.
Once the branch is ready, ensure your local environment is configured for V8 development:
export PATH=$PATH:$HOME/depot_toolsout/x64.debug).