github.com/nodejs/node (link)

commit signals (317)

source signals (34)

• deps/v8/agents/skills/subagent-env-passing/SKILL.mdvia unspecified

  ---
  name: subagent-env-passing
  description: Workflow for passing environment variables (like PATH) from the Orchestrator to subagents. Use when spawning subagents that need specific environment variables. Do not use for standard subagent execution.
  ---
  
  # Subagent Environment Passing Skill
  
  This skill documents how to ensure subagents have access to the correct
  environment variables (such as `PATH`) when working in isolated environments
  like worktrees.
  
  ## Workflow
  
  1. **Retrieve Environment**: The Orchestr

• deps/v8/agents/skills/crossbench/SKILL.mdvia unspecified

  ---
  name: crossbench
  description: Running benchmarks with Crossbench.
  ---
  
  # Crossbench
  
  Crossbench is the central chrome runner harness for press benchmarks like
  JetStream, Speedometer or Motionmark, as well as for loading live pages.
  
  ## Location and Setup
  
  - **Location**: It is often installed in `~/crossbench` or in
    `CHROMIUM_CHECKOUT/src/tools/perf/cb`, but could be anywhere. If not found in
    standard locations, ask the user for the path.
  - **Update**: Always ensure you are running the latest versio

• deps/v8/agents/skills/v8-commands/SKILL.mdvia unspecified

  ---
  name: v8-commands
  description: Key commands for building, debugging, and testing in V8. Use when needing command syntax for gm.py, d8 flags, or run-tests.py. Do not use for environment setup.
  ---
  
  # V8 Key Commands
  
  Use this skill to find the correct commands for common development tasks in V8.
  This unifies the commands listed in workspace configuration and ensures
  consistent usage.
  
  ## Building
  
  V8 uses `gm.py` as a wrapper around GN and Ninja for building.
  
  **Mandatory GN Args & Siso Remote Execution 

• deps/v8/agents/skills/v8-profile/SKILL.mdvia unspecified

  ---
  name: v8-profile
  description: Profiling V8 execution.
  ---
  
  # V8 Profiling
  
  This skill explains how to profile V8 execution using native tools to understand
  where time is spent. Make sure to only profile on a quiet system to get the best
  results.
  
  ## Linux Profiling
  
  On Linux, prefer using the `./tools/profiling/linux-perf-d8.py` script. This
  script automates the process of running Linux `perf` with V8, and critically, it
  runs `perf inject --jit` afterwards to ensure that JIT-compiled JavaScript
  function

• deps/v8/agents/skills/orchestrator/SKILL.mdvia unspecified

  ---
  name: orchestrator
  description: Core skill for task scheduling and multi-agent coordination in V8 development. Use for any multi-step workflow or complex task. Do not use for simple linear tasks.
  ---
  
  # Orchestrator Skill
  
  This skill defines the behavior of the Main Agent acting as an Orchestrator and
  Scheduler. It is mandatory for all complex tasks to ensure efficiency,
  parallelism, and correct dependency handling.
  
  ## Core Responsibilities
  
  1. **Task Breakdown & DAG Construction**:
  
     - Analyze the h

• deps/v8/agents/skills/workflow-perf/SKILL.mdvia unspecified

  ---
  name: workflow-perf
  description: Workflow for performance and memory evaluation in V8. Use when tasked with improving the performance or memory usage of a workload in V8. Do not use when debugging a crash or functionality issue.
  ---
  
  # Workflow: Performance Evaluation
  
  Use this skill when tasked with improving the performance or memory usage of a
  workload in V8. This workflow focuses on identifying bottlenecks and applying
  V8-side optimizations.
  
  ## Activation Criteria
  
  - User requests to optimize a spe

• deps/v8/agents/skills/v8-understanding/SKILL.mdvia unspecified

  ---
  name: v8-understanding
  description: Guides the methodology for investigating V8 concepts, codebase structure, performance, memory, and architecture. MANDATORY to use whenever triaging bugs, investigating crashes, reading C++ files, analyzing compiler optimizations (Ignition, Maglev, TurboFan, Turboshaft), or doing static research on V8 subsystems. Essential for locating high-level design documents in the local docs/ directory before reading C++ code. Do not use for raw build commands or Git workflows.
  -

• deps/v8/agents/skills/v8-security-triaging/SKILL.mdvia unspecified

  ---
  name: v8-security-triaging
  description: Guides the initial analysis and impact assessment of a V8 security report, strictly excluding implementation or fixing.
  ---
  
  # Skill: V8 Security Triaging
  
  Use this skill to orchestrate the initial analysis and impact assessment of a V8
  security vulnerability report.
  
  ## Core Mandates
  
  - **Strategic Orchestration**: You are the **Orchestrator**. Your goal is to
    manage specialized subagents to verify reporter claims empirically while
    keeping your own context le

• deps/v8/agents/skills/clangd-setup/SKILL.mdvia unspecified

  ---
  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.
  ---
  
  # Clangd Setup Skill
  
  Use this skill when `clangd-mcp` is missing or needs configuration for the
  current workspace.
  
  ## Core Principles
  
  - **Proactive Execution**: Do all necessary work to set up `clangd` once user
    approval is obtained.
  - **Workspace Specific**: Configuration (`compile_comm

• deps/v8/agents/skills/env-abstraction/SKILL.mdvia unspecified

  ---
  name: env-abstraction
  description: 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.
  ---
  
  # Environment Abstraction Skill
  
  This skill provides a layer of abstraction over environment-specific tools and
  commands, allowing skills to be reused across different platforms like `jetski`
  and `gemini-cli`.
  
  ## Core Principles
  
  1. **Decoupling**: Keep tool calls indep

• deps/v8/agents/skills/header-cycle-breaker/SKILL.mdvia unspecified

  ---
  name: header-cycle-breaker
  description: Guide for breaking cyclic dependencies in V8 headers and resolving cascade IWYU failures.
  ---
  
  # Header Cycle Breaker Skill
  
  This skill outlines the systematic approach to breaking cyclic dependencies in
  V8 headers, specifically focusing on moving heavy inline includes to more
  localized `.cc` files or non-inline headers, and resolving the resulting cascade
  of "undefined inline function" errors (IWYU - Include What You Use style).
  
  ## When to Use
  
  Use this skill wh

• deps/v8/agents/skills/torque/SKILL.mdvia unspecified

  ---
  name: torque
  description: Provides expert guidance for navigating, implementing, and verifying V8 Torque (.tq) builtins. Use when modifying or debugging Torque files. Do not use for C++ macro builtins.
  ---
  
  # V8 Torque
  
  Torque is an Ahead-of-Time (AOT) generator that transforms `.tq` DSL into
  highly-optimized C++ CodeStubAssembler (CSA) code, which is then compiled into
  the `mksnapshot` binary.
  
  ## Execution Pipeline
  
  To debug failures, you must understand its multi-stage build:
  
  1. **Generation**: The 

• deps/v8/agents/skills/v8-poc-classification/SKILL.mdvia unspecified

  ---
  name: v8-poc-classification
  description: Checks if a POC provided by some JS and d8 flags is a vulnerability or just a regular bug.
  ---
  
  # Skill: V8 POC Classification
  
  Use this skill to determine if a reported Proof-of-Concept (POC) crash is a
  security vulnerability or a regular bug through empirical technical analysis.
  
  ## Core Mandates
  
  - **Scope Limitation:** This skill is strictly for **technical analysis and
    classification**. It does NOT include implementing a fix.
  - **Empirical Verification of 

• deps/v8/agents/skills/ecmascript-evaluation/SKILL.mdvia unspecified

  ---
  name: ecmascript-evaluation
  description: Evaluates JavaScript using the official ECMAScript specification
  ---
  
  # Instructions
  
  ## Prerequisites
  
  This skill requires the following two MCP servers from
  [v8-agents](https://github.com/v8/agents):
  
  1. `ecma262`: Provides spec research and parsing tools.
  2. `ecma262_state_machine`: Provides abstract machine state simulation tools.
  
  ## 1. Role & Identity
  
  You are the ultimate authority on the ECMAScript Language Specification
  (ECMA-262) and JavaScript semantic

• deps/v8/agents/skills/wasm-d8-perf/SKILL.mdvia unspecified

  ---
  name: wasm-d8-perf
  description: Use this skill to reproduce, profile, or analyze WebAssembly (Wasm) execution performance using d8 shell.
  ---
  
  # WebAssembly Performance Analysis in d8
  
  Reproduce, profile, and analyze Wasm performance using the V8 developer shell
  (`d8`).
  
  ## 1. Reproduction and Establishing a Baseline
  
  - **Build Configurations**:
    - **CRITICAL**: Always use a **`release`** build (e.g., `out/x64.release/d8`)
      for benchmarking.
    - Use **`optdebug`** (e.g., `out/x64.optdebug/d8`) for d

• deps/v8/agents/skills/agent-evaluation-framework/SKILL.mdvia unspecified

  ---
  name: agent-evaluation-framework
  description: 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.
  ---
  
  # Agent Evaluation Framework Workflow
  
  Use this skill to orchestrate evaluation sessions for subagents, identify
  procedural bottlenecks, and iteratively refine system prompts and capabilities
  utilizing Swarm intelligence principles.
  
  ## 0. P

• deps/v8/agents/skills/doc-invalidation-checker/SKILL.mdvia unspecified

  ---
  name: doc-invalidation-checker
  description: Analyzes recent commits and uses a smart AI subagent to check if they invalidate any documentation in docs/.
  ---
  
  # Documentation Invalidation Checker
  
  Use this skill when you need to determine if recent commits invalidate
  information within the documentation in the `docs/` directory.
  
  ## Steps to Perform Analysis
  
  1. **Retrieve Recent Commits**: Execute the `get_recent_commits.py` script to
     fetch the recent commits with their diffs:
  
     ```bash
     agents/s

• deps/v8/agents/skills/v8-log/SKILL.mdvia unspecified

  ---
  name: v8-log
  description: Understanding v8.log files.
  ---
  
  # V8 Log Viewer CLI
  
  A standalone command-line tool for analyzing `v8.log` files. It allows you to
  inspect internal state of the V8 JavaScript engine.
  
  ## Requirements
  
  This tool requires the V8 shell (`d8`) to be installed and accessible. If no
  local d8 build is available it will try to call back to jsvu's d8 in
  `~/.jsvu/bin/v8`. You can override this by setting the `V8_PATH` environment
  variable.
  
  ## Available Commands
  
  Use the following comma

• deps/v8/agents/skills/v8-testing/SKILL.mdvia unspecified

  ---
  name: v8-testing
  description: Executes and interprets V8 tests. Use when running unittests, cctest, or mjsunit, or when debugging test failures. Do not use for building.
  ---
  
  # V8 Testing
  
  Use this skill to understand how to run tests in V8 and how to handle failures.
  This specializes the general commands for testing.
  
  ## Primary Script
  
  The primary script for running tests is `tools/run-tests.py`. You specify the
  build output directory and the tests you want to run.
  
  ## Key Test Suites
  
  - **unittests**

• deps/v8/agents/skills/agent-self-improvement/SKILL.mdvia unspecified

  ---
  name: agent-self-improvement
  description: 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.
  ---
  
  # Agent Self-Improvement Workflow
  
  Use this skill to orchestrate self-improvement sessions for agents. The workflow
  involves running debugging or implementation tasks in isolation, evaluating the
  results against known good solutions, and identifying improvements

• deps/v8/agents/skills/v8-regression-testing/SKILL.mdvia unspecified

  ---
  name: v8-regression-testing
  description: Use this skill when designing, writing, or minimizing regression tests (e.g., mjsunit) for V8 bug fixes
  ---
  
  # Skill: V8 Regression Testing
  
  Use this skill to design, write, minimize, and refine high-quality regression
  tests in the V8 codebase (typically under `test/mjsunit/` or its
  component-specific subfolders like `compiler/`, `turboshaft/`, `maglev/`, etc.).
  
  ## Core Mandates
  
  - **Mandatory Reproducer Rule**: Unless explicitly specified otherwise by the
    use

• deps/v8/agents/skills/jsvu/SKILL.mdvia unspecified

  ---
  name: jsvu
  description: How to use jsvu for cross-engine testing.
  ---
  
  # JSVU (JavaScript engine Version Updater)
  
  Use `jsvu` to install and test across multiple JavaScript engines (e.g., v8,
  spidermonkey, javascriptcore, chakra).
  
  ## Installation and Setup
  
  For non-interactive installation and updating of specific engines on Linux, run:
  
  ```bash
  npx jsvu --os=linux64 --engines=v8,spidermonkey,javascriptcore
  ```
  
  You can customize the `--engines` flag with the engines you wish to test (e.g.,
  `v8,v8-debu

• deps/v8/agents/skills/workflow-debugging/SKILL.mdvia unspecified

  ---
  name: workflow-debugging
  description: 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: Issue Debugging
  
  Use this skill when tasked with debugging a specific issue, usually associated
  with a Buganizer ID or a specific reproduction script. This specializes the
  general debugging approach for tracked issues.
  
  ## Activation Criteria
  
  - Us

• deps/v8/agents/skills/v8-setup/SKILL.mdvia unspecified

  ---
  name: v8-setup
  description: Handles missing dependencies and configuration for V8 tools. Use when encountering missing tools, test runners, or workspace symlinks. Do not use for C++ coding issues.
  ---
  
  # Skill: V8 Setup
  
  Use this skill to handle missing dependencies or configuration issues in the V8
  environment.
  
  ## Workspace Setup for Jetski
  
  Jetski often expects a `.agents` directory or symlink in the V8 workspace root
  to find skills and rules.
  
  - **Missing `.agents`**: If the workspace only has `agen

• deps/v8/agents/skills/v8-structure/SKILL.mdvia unspecified

  ---
  name: v8-structure
  description: Maps the V8 dir/folder structure, component locations, and local documentation. Use when locating specific subsystems, mapping src/ code to docs/ design files, or understanding repository architecture.
  ---
  
  # V8 Folder Structure
  
  Use this skill to understand the layout of the V8 repository and locate specific
  components.
  
  ## Main Directories
  
  - `src/`: The main source folder providing the implementation of the virtual
    machine. Key subdirectories include:
    - `src/api/`:

• deps/v8/agents/plugins/trace_processor/skills/trace_processor/SKILL.mdvia unspecified

  ---
  name: trace_processor
  description: Managing and querying Perfetto traces using the trace_processor MCP server.
  ---
  
  # Trace Processor
  
  The `trace_processor` extension launches a long-running FastMCP server wrapping
  Perfetto's trace processor capabilities, allowing seamless interaction with
  trace files (`.pftrace`, `.perfetto-trace`, `.pb`).
  
  ## Writing PerfettoSQL and Schema Analysis
  
  For comprehensive guidance on querying traces, utilizing standard library
  modules, and schema structures, refer directly

• deps/v8/agents/skills/minimize-reproducer/SKILL.mdvia unspecified

  ---
  name: minimize-reproducer
  description: Use this when you need to minimize a complex or bloated JavaScript test case (e.g., from a fuzzer or external report) into a minimal, readable reproduction for debugging V8 issues.
  ---
  
  # Minimize Reproducer
  
  ## Workflow
  
  ### 1. Identify the Failure Signature
  
  Before minimizing, understand exactly what "reproduction" looks like.
  
  - **Exact Command:** e.g., \`out/x64.release/d8 --fuzzing poc.js\`
  - **Failure Type:** Crash (segfault, abort), Assertion failure, Sandbo

• deps/v8/agents/skills/v8-ciderg-paths/SKILL.mdvia unspecified

  ---
  name: v8-ciderg-paths
  description: Adjusts instructions for V8 commands when running in a CiderG Chrome workspace environment. Trigger this when invoking any V8 binaries or running tests in a CiderG checkout.
  ---
  
  # V8 CiderG Path Adjustments
  
  Because CiderG nests the V8 repository as a component of a larger Chromium
  checkout, the build output (`out/` directory) is generated at the root of the
  Chromium checkout rather than the V8 directory.
  
  ## Path Rules
  
  - When executing from `chromium/v8`, the build 

• deps/v8/agents/skills/v8-workflow/SKILL.mdvia unspecified

  ---
  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.
  ---
  
  # V8 Workflow Skill
  
  This skill defines the standard process for setting up and managing your
  development environment in V8.
  
  ## 1. Task Initialization (Isolation Strategy)
  
  Before starting any feature or bug fix, you MUST decide on a strategy:
  
  - **Isolated Strategy (Recommended)**: Create a dedicated git worktree and
    branch. This

• deps/v8/agents/skills/workflow-general-debugging/SKILL.mdvia unspecified

  ---
  name: workflow-general-debugging
  description: 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.
  ---
  
  # Skill: Workflow - General Debugging
  
  Workflow for general debugging tasks in a pristine branch or project work,
  without the overhead of issue tracking. Use this skill when investigating
  crashes, hangs, or unexpected behavior where no spec

• deps/v8/agents/skills/workflow-gerrit-fix/SKILL.mdvia unspecified

  ---
  name: workflow-gerrit-fix
  description: Workflow for automatically fixing errors or addressing comments on a Gerrit CL requested by the user.
  ---
  
  # Gerrit Fix & Review Workflow
  
  Use this skill when the user asks to "fix the errors on Gerrit issue X" or
  "address reviewer comments on CL X" or similar requests targeting a specific
  Gerrit Change List (CL).
  
  ## Core Principles
  
  1. **Orchestration**: Do not do the work yourself. Break down the task and
     delegate to subagents.
  2. **Parallelism**: Always iden

• AGENTS.mdvia agents-md

  # Agents and Automated Tools
  
  This document outlines rules and requirements for AI automation agents and automated
  tooling that interact with the Node.js project.
  
  Existing Node.js collaborators (as listed in the README.md) may use AI agents to
  contribute but must do so responsibly.
  
  New Node.js contributors should avoid using AI agents to interact with the project.
  
  ## Code Contributions
  
  * **No unreviewed automation**: Automated pull requests must not be created without
    ongoing human oversight. The pull

• deps/undici/src/docs/docs/api/Agent.mdvia agents-md

  # Agent
  
  <!--introduced_in=v3.2.0-->
  <!--type=module-->
  <!-- source_link=lib/dispatcher/agent.js -->
  
  > Stability: 2 - Stable
  
  An `Agent` dispatches requests against multiple different origins, creating and
  reusing a per-origin [`Pool`][] (or [`Client`][]) on demand. It is the default
  dispatcher used by [`request`][], [`stream`][], and [`fetch`][] when no explicit
  dispatcher is supplied.
  
  Requests are not guaranteed to be dispatched in their order of invocation.
  
  ```mjs
  import { Agent, setGlobalDispatcher }

• deps/npm/node_modules/undici/docs/docs/api/Agent.mdvia agents-md

  # Agent
  
  Extends: `undici.Dispatcher`
  
  Agent allow dispatching requests against multiple different origins.
  
  Requests are not guaranteed to be dispatched in order of invocation.
  
  ## `new undici.Agent([options])`
  
  Arguments:
  
  * **options** `AgentOptions` (optional)
  
  Returns: `Agent`
  
  ### Parameter: `AgentOptions`
  
  Extends: [`PoolOptions`](Pool.md#parameter-pooloptions)
  
  * **factory** `(origin: URL, opts: Object) => Dispatcher` - Default: `(origin, opts) => new Pool(origin, opts)`
  * **maxRedirections** `Integ

ignorefile signals (9)