// Handles installation and configuration of clangd-mcp for V8. Use when clangd-mcp is missing or needs configuration for the current workspace. Do not use for general C++ editing.
Workflow for evaluating and refining agent debugging capabilities using designated test cases and Swarm principles. Use when evaluating subagent performance or creating benchmarks. Do not use for regular bug fixing.
Workflow for agent self-improvement via isolated execution, evaluation, and process refinement. Use when evaluating historical bugs or self-correcting skills. Do not use for new feature development.
Running benchmarks with Crossbench.
Analyzes recent commits and uses a smart AI subagent to check if they invalidate any documentation in docs/.
Evaluates JavaScript using the official ECMAScript specification
Handles abstraction of environment-specific commands between Jetski and Gemini-CLI. Use when switching execution context between local terminal environments. Do not use for debugging logic issues.
| name | clangd-setup |
| description | Handles installation and configuration of clangd-mcp for V8. Use when clangd-mcp is missing or needs configuration for the current workspace. Do not use for general C++ editing. |
Use this skill when clangd-mcp is missing or needs configuration for the current workspace.
clangd once user approval is obtained.compile_commands.json) must be generated for the specific V8 checkout.Follow these steps to ensure clangd is ready:
clangd-mcpclangd-mcp server is available in the list of registered servers.clangd-mcp for this workspace?"compile_commands.jsonclangd requires a compilation database to understand the codebase.
out/x64.debug, out/x64.release.compile_commands.json already exists in the identified build directory or at the project root.gn gen <build_dir> --export-compile-commands.
gn gen out/x64.debug --export-compile-commandscompile_commands.json is generated, verify that clangd-mcp tools (like find_symbol, get_definition) return meaningful results for a known symbol in the codebase.clangd cannot find headers, ensure compile_commands.json is at the root or linked correctly, and that the build has been run at least once to generate all necessary headers (like Torque generated files).