chrome-devtools-frontend 1.0.1667564 → 1.0.1669021

package/.agents/skills/devtools-ci/SKILL.md

@@ -0,0 +1,65 @@
+---
+name: devtools-ci
+description: >-
+  Triage and analyze Chromium/DevTools LUCI build results and trybot failures,
+  including high-level builder status, compile errors, and detailed test
+  failures. Use this to inspect trybot buildbucket (bb) results for a patchset
+  overview or to query ResultDB directly for comprehensive, actionable information
+  about specific test regressions and infrastructure issues.
+---
+
+# LUCI Build Triage & Analysis
+
+This skill provides access to specialized triage tools maintained within the
+`depot_tools` repository. These tools are used to inspect Buildbucket results
+and ResultDB test failures.
+
+## Environment & Auth Discovery
+
+- **Environment**: Always execute these scripts using **`vpython3`** instead
+  of `python3` to ensure all hermetic dependencies (like `httplib2`) are
+  satisfied.
+- **Authentication**: Use `bb auth-info` to proactively check if you are
+  logged into Buildbucket. If not, inform the user they must run `bb auth-login`.
+
+## Locating the Tools
+
+The triage scripts and their detailed documentation are located relative to
+the `depot_tools` installation:
+
+1.  **Locate Depot Tools**: Run `which gerrit_client.py` to find your local
+    `depot_tools` root.
+2.  **Navigation**:
+    - **Buildbucket (`bb_wrapper.py`)**: Found in `<DEPOT_TOOLS_ROOT>/agents/skills/buildbucket/`
+      - *Strengths*: High-level Build info (is it failing? what steps failed?),
+        compile errors, and infra issues.
+    - **Test Results (`luci_triage.py`)**: Found in `<DEPOT_TOOLS_ROOT>/agents/skills/luci-test-results/`
+      - *Strengths*: Detailed Test info (specific test case failures in
+        ResultDB).
+
+## Troubleshooting
+
+- **"No Artifacts Found"**: This usually occurs if:
+  1. The build failed so early (e.g., bot setup) that no artifacts were produced.
+  2. The build is too old and logs have been purged.
+  3. There is an authentication issue.
+  - **Fallback**: Try `bb log <build_id> <step_name>` to see the raw output
+    for the failed step.
+
+## Available Skills in Depot Tools
+
+Once you have located the `depot_tools` directory, read the following files
+to understand how to use each tool:
+
+- **`buildbucket`**: Used for high-level builder status and compile failures.
+  - Read: `<DEPOT_TOOLS_ROOT>/agents/skills/buildbucket/SKILL.md`
+- **`luci-test-results`**: Used for detailed ResultDB test failure analysis.
+  - Read: `<DEPOT_TOOLS_ROOT>/agents/skills/luci-test-results/SKILL.md`
+
+## Usage at Runtime
+
+When you need to triage a build:
+1.  Locate `depot_tools` as described above.
+2.  Read the relevant `SKILL.md` file from `depot_tools`.
+3.  Follow the instructions in that file to execute the Python scripts (e.g.,
+    `bb_wrapper.py` or `luci_triage.py`) using their absolute paths.

package/.agents/skills/devtools-setting-migration/SKILL.md

@@ -0,0 +1,290 @@
+---
+name: devtools-setting-migration
+description: "Workflow for splitting an existing SettingRegistration into a SettingDescriptor (placed in the lowest layer where used: core/, models/, or ui/settings/) and SettingUIDescriptor (registered in a higher-level -meta.ts file, outside of core/ and models/)."
+---
+
+# DevTools Setting Migration Guide
+
+This skill guide describes how to migrate an existing legacy `SettingRegistration` in DevTools by splitting it into a `SettingDescriptor` (non-UI descriptor) and a `SettingUIDescriptor` (UI descriptor).
+
+---
+
+## Key Principles & Layer Boundaries
+
+### 1. `SettingDescriptor` Location ("Lowest Layer")
+* **Lowest Layer Rule:** A `SettingDescriptor` MUST be placed in the lowest architectural layer where the setting is used.
+  * **Core / Model Settings:** If a setting is used by `core/sdk` (or `models/`), its `SettingDescriptor` should be located in `core/sdk` (or `models/`).
+  * **Panel / UI Settings:** If a setting is only used by UI components or a specific panel (e.g. `panels/console/`), its `SettingDescriptor` **MUST GO INTO `ui/settings/FooSettings.ts`** (e.g. `ui/settings/ConsoleSettings.ts` where `Foo` is the panel name).
+* **CRITICAL RULE — PANEL DESCRIPTORS MUST NOT BE PLACED IN `panels/`:**
+  * A `SettingDescriptor` **MUST NOT** be placed inside a `panels/` directory (e.g. `panels/console/ConsoleSettings.ts`).
+  * **Reason:** Panel `-meta.ts` files (e.g. `panels/console/console-meta.ts`) need to import the `SettingDescriptor` to call `SettingsUI.SettingUIRegistration.register(descriptor, uiDescriptor)`. `-meta.ts` files are loaded early and **MUST NOT import from `panels/`** (which would break lazy-loading of panel bundles). Since `ui/settings/` is in the `ui/` layer below `panels/`, `-meta.ts` files can safely import from `ui/settings/`.
+* **CRITICAL RULE — MUST NOT BE IN A `-meta.ts` FILE:**
+  * A `SettingDescriptor` **MUST NOT** be placed in a `-meta.ts` file.
+  * **Reason:** Actual runtime code (e.g. models, panels, SDKs) needs to import the descriptor directly to call `Settings.instance().resolve(descriptor)`. Preload `-meta.ts` files are meant for lazy-loaded extension registrations and must not be imported by runtime code to avoid circular dependencies and module boundary violations.
+
+### 2. `SettingUIDescriptor` Location (Higher-Level `-meta.ts` File)
+* A `SettingUIDescriptor` defines UI-specific properties (category, title, tags, options, reload requirement, etc.).
+* **Higher-Level Meta File Rule:** UI registrations **MUST BE PLACED IN A `-meta.ts` FILE ON A HIGHER LEVEL** (e.g., `entrypoints/main/main-meta.ts`, `entrypoints/inspector_main/inspector_main-meta.ts`, `panels/settings/settings-meta.ts`, or the specific panel's `-meta.ts` file).
+* **CRITICAL RULE — MUST NOT REMAIN IN `core/` OR `models/`:**
+  * UI descriptors **MUST NOT** remain in or be added to `-meta.ts` files under `core/` or `models/` (such as `core/sdk/sdk-meta.ts` or `models/*/*-meta.ts`).
+  * **Goal:** A major goal of this migration is to completely eliminate `-meta.ts` files in `core/` and `models/`.
+
+### 3. Resolving Settings vs `moduleSetting(name)`
+* Legacy code retrieves settings using string identifiers: `Settings.instance().moduleSetting('setting-name')`.
+* Refactored code should replace `moduleSetting('setting-name')` with `Settings.instance().resolve(settingDescriptor)`.
+
+---
+
+## Step-by-Step Migration Workflow
+
+Given a setting name (e.g., `'preserve-console-log'` or `'network-messages'`):
+
+### Step 1: Locate Existing Registration & Analyze Use-Sites
+1. Search for the setting name in `-meta.ts` files to find its `Common.Settings.registerSettingExtension` block.
+2. Search for all occurrences of `'setting-name'` or `moduleSetting('setting-name')` across the codebase to identify all use-sites.
+3. Determine the **lowest layer** among all use-sites:
+   * If used in `core/sdk` -> Target directory is `core/sdk/`.
+   * If used in `models/` -> Target directory is `models/<module>/`.
+   * If used in a panel (`panels/foo`) or UI -> Target directory is **`ui/settings/`** (file: `ui/settings/FooSettings.ts`). **NEVER place descriptors in `panels/`**.
+
+---
+
+### Step 2: Extract & Define `SettingDescriptor` in the Lowest Layer
+
+#### Decision Strategy: Create vs. Update File
+When placing a `SettingDescriptor` in the target directory, decide whether to create or update a file using these rules:
+
+1. **For Panel / UI Settings (Target is `ui/settings/`)**:
+   * **UPDATE**: Check if `ui/settings/FooSettings.ts` already exists (e.g., `ui/settings/ConsoleSettings.ts`). If so, add and export the `SettingDescriptor` there.
+   * **CREATE**: If `ui/settings/FooSettings.ts` does not exist:
+     * Create `ui/settings/FooSettings.ts`.
+     * Add `FooSettings.ts` to `sources` in `ui/settings/BUILD.gn`.
+     * Export `FooSettings.ts` from `ui/settings/settings.ts`.
+
+2. **For Core / Model Settings (Target is `core/` or `models/`)**:
+   * **UPDATE**: Check if a module-wide settings file exists in that directory (e.g. `core/sdk/SDKSettings.ts`, `models/workspace/WorkspaceSettings.ts`). If so, add and export the `SettingDescriptor` there.
+   * **UPDATE**: If no module settings file exists and the setting is strictly used inside a single file (e.g., `ResourceTreeModel.ts`), update that `.ts` file by exporting the `SettingDescriptor` at the top.
+   * **CREATE**: Otherwise, create `<Module>Settings.ts` (e.g., `core/sdk/SDKSettings.ts`), add it to `sources` in `BUILD.gn`, and export it from the module's entrypoint (`sdk.ts`).
+
+#### Code Definition Example:
+Define and export the `SettingDescriptor` in the target file:
+
+```typescript
+import type * as Common from '../core/common/common.js';
+
+export const preserveConsoleLogSettingDescriptor: Common.Settings.SettingDescriptor<boolean> = {
+  name: 'preserve-console-log',
+  type: Common.Settings.SettingType.BOOLEAN,
+  defaultValue: false,
+  storageType: Common.Settings.SettingStorageType.SYNCED,
+};
+```
+
+*Note: For conditional settings (dependent on `hostConfig`), use `Common.Settings.ConditionalSettingDescriptor<ValueT, ReasonT>` with an `isAvailable` function.*
+
+---
+
+### Step 3: Move UI Registration to a Higher-Level `-meta.ts` File
+If the original registration was in a `core/` or `models/` `-meta.ts` file (e.g., `core/sdk/sdk-meta.ts`), **MOVE** the UI registration to a higher-level `-meta.ts` file (e.g., `entrypoints/main/main-meta.ts` or `panels/console/console-meta.ts`).
+
+In the higher-level `-meta.ts` file:
+1. Import `SettingsUI` from `ui/settings/settings.js` (e.g., `import * as SettingsUI from '../../ui/settings/settings.js';`).
+2. Import the `SettingDescriptor` (from `core/sdk/`, `models/`, or `ui/settings/`).
+3. Register using `SettingsUI.SettingUIRegistration.register(...)`:
+
+```typescript
+import * as SettingsUI from '../../ui/settings/settings.js';
+import * as SDK from '../../core/sdk/sdk.js';
+
+SettingsUI.SettingUIRegistration.register(SDK.SDKSettings.preserveConsoleLogSettingDescriptor, {
+  category: Common.Settings.SettingCategory.CONSOLE,
+  title: i18nLazyString(UIStrings.preserveLogUponNavigation),
+  options: [
+    {
+      value: true,
+      title: i18nLazyString(UIStrings.preserveLogUponNavigation),
+    },
+    {
+      value: false,
+      title: i18nLazyString(UIStrings.doNotPreserveLogUponNavigation),
+    },
+  ],
+});
+```
+
+4. **Delete** the old `Common.Settings.registerSettingExtension` call from the `core/` or `models/` `-meta.ts` file. (If the `-meta.ts` file becomes empty, delete the file and clean up its build references).
+
+---
+
+### Step 4: Update Call Sites (`moduleSetting` to `resolve`)
+Find all call sites referencing the setting via `moduleSetting`:
+
+```typescript
+// BEFORE:
+const setting = Common.Settings.Settings.instance().moduleSetting('preserve-console-log');
+
+// AFTER:
+import { preserveConsoleLogSettingDescriptor } from './SDKSettings.js';
+...
+const setting = Common.Settings.Settings.instance().resolve(preserveConsoleLogSettingDescriptor);
+```
+
+*For conditional settings, use `Common.Settings.Settings.instance().maybeResolve(descriptor)` instead of `resolve(descriptor)`.*
+
+---
+
+### Step 5: Update `BUILD.gn` Files and Module Entrypoints
+1. If a new `.ts` file was created (e.g., `SDKSettings.ts` or `ui/settings/ConsoleSettings.ts`):
+   * Add the file to `sources` in its module's `BUILD.gn`.
+   * Export the file from the module's entrypoint (`sdk.ts`, `settings.ts`, etc.).
+2. If a `core/` or `models/` `-meta.ts` file was deleted, remove it from `BUILD.gn` and `devtools_grd_files.gni`.
+3. Verify module imports strictly follow DevTools import rules (refer to `devtools-imports` skill).
+
+---
+
+### Step 6: Verify Changes
+1. Run `autoninja -C out/Default` to check GN build.
+2. Run `npm run lint` to check style and formatting rules.
+3. Run relevant unit tests for the modified module.
+
+---
+
+## Concrete Examples
+
+### Example 1: Core/SDK Setting Migration (`preserve-console-log`)
+
+#### Before Migration
+Setting registered in **`front_end/core/sdk/sdk-meta.ts`** *(Legacy core meta file)*:
+```typescript
+Common.Settings.registerSettingExtension({
+  category: Common.Settings.SettingCategory.CONSOLE,
+  storageType: Common.Settings.SettingStorageType.SYNCED,
+  title: i18nLazyString(UIStrings.preserveLogUponNavigation),
+  settingName: 'preserve-console-log',
+  settingType: Common.Settings.SettingType.BOOLEAN,
+  defaultValue: false,
+  options: [...],
+});
+```
+
+Setting used in **`front_end/core/sdk/ResourceTreeModel.ts`**:
+```typescript
+const setting = Common.Settings.Settings.instance().moduleSetting('preserve-console-log');
+```
+
+---
+
+#### After Migration
+
+1. **`front_end/core/sdk/SDKSettings.ts`** *(Lowest Layer in Core — NOT a `-meta.ts` file)*:
+```typescript
+import type * as Common from '../common/common.js';
+
+export const preserveConsoleLogSettingDescriptor: Common.Settings.SettingDescriptor<boolean> = {
+  name: 'preserve-console-log',
+  type: Common.Settings.SettingType.BOOLEAN,
+  defaultValue: false,
+  storageType: Common.Settings.SettingStorageType.SYNCED,
+};
+```
+
+2. **`front_end/entrypoints/main/main-meta.ts`** *(Higher-Level Meta File — NOT in `core/` or `models/`)*:
+```typescript
+import * as SDK from '../../core/sdk/sdk.js';
+import * as SettingsUI from '../../ui/settings/settings.js';
+
+SettingsUI.SettingUIRegistration.register(SDK.SDKSettings.preserveConsoleLogSettingDescriptor, {
+  category: Common.Settings.SettingCategory.CONSOLE,
+  title: i18nLazyString(UIStrings.preserveLogUponNavigation),
+  options: [...],
+});
+```
+
+3. **`front_end/core/sdk/ResourceTreeModel.ts`** *(Call Site in `core/sdk`)*:
+```typescript
+import { preserveConsoleLogSettingDescriptor } from './SDKSettings.js';
+
+const setting = Common.Settings.Settings.instance().resolve(preserveConsoleLogSettingDescriptor);
+```
+
+4. **`front_end/core/sdk/sdk-meta.ts`**:
+Registration for `'preserve-console-log'` removed.
+
+---
+
+### Example 2: Panel UI Setting Migration (`network-messages`)
+
+#### Before Migration
+Setting registered in **`front_end/panels/console/console-meta.ts`**:
+```typescript
+Common.Settings.registerSettingExtension({
+  category: Common.Settings.SettingCategory.CONSOLE,
+  storageType: Common.Settings.SettingStorageType.SYNCED,
+  title: i18nLazyString(UIStrings.networkMessages),
+  settingName: 'network-messages',
+  settingType: Common.Settings.SettingType.BOOLEAN,
+  defaultValue: true,
+  options: [...],
+});
+```
+
+Setting used in **`front_end/panels/console/ConsoleView.ts`**:
+```typescript
+const setting = Common.Settings.Settings.instance().moduleSetting('network-messages');
+```
+
+---
+
+#### After Migration
+
+1. **`front_end/ui/settings/ConsoleSettings.ts`** *(Lowest Layer for UI/Panel Descriptor — NOT in `panels/console/`!)*:
+```typescript
+import type * as Common from '../../core/common/common.js';
+
+export const networkMessagesSettingDescriptor: Common.Settings.SettingDescriptor<boolean> = {
+  name: 'network-messages',
+  type: Common.Settings.SettingType.BOOLEAN,
+  defaultValue: true,
+  storageType: Common.Settings.SettingStorageType.SYNCED,
+};
+```
+
+2. **`front_end/panels/console/console-meta.ts`** *(Panel Meta File — Imports Descriptor from `ui/settings/`)*:
+```typescript
+import * as SettingsUI from '../../ui/settings/settings.js';
+
+SettingsUI.SettingUIRegistration.register(SettingsUI.ConsoleSettings.networkMessagesSettingDescriptor, {
+  category: Common.Settings.SettingCategory.CONSOLE,
+  title: i18nLazyString(UIStrings.networkMessages),
+  options: [...],
+});
+```
+
+3. **`front_end/panels/console/ConsoleView.ts`** *(Call Site in `panels/console`)*:
+```typescript
+import * as SettingsUI from '../../ui/settings/settings.js';
+
+const setting = Common.Settings.Settings.instance().resolve(SettingsUI.ConsoleSettings.networkMessagesSettingDescriptor);
+```
+
+---
+
+## Interface Reference Summary
+
+### `SettingDescriptor<T>`
+Defined in `core/common/Settings.ts`:
+* `name: string`: Unique setting name (kebab-case).
+* `type: SettingType`: `BOOLEAN`, `ENUM`, `ARRAY`, or `REGEX`.
+* `defaultValue: ValueT | ((hostConfig: HostConfig) => ValueT)`: Default setting value.
+* `storageType?: SettingStorageType`: `SYNCED`, `LOCAL`, `GLOBAL`, or `SESSION`.
+
+### `SettingUIDescriptor`
+Defined in `ui/settings/SettingUIRegistration.ts`:
+* `category?: SettingCategory`: Category under which setting is listed in Settings UI.
+* `order?: number`: Sorting order.
+* `title?: () => LocalizedString`: Title string displayed in Settings UI.
+* `tags?: Array<() => LocalizedString>`: Search tags for Command Menu.
+* `options?: SettingExtensionOption[]`: Enum / boolean option descriptions.
+* `reloadRequired?: boolean`: Whether setting change requires DevTools reload.
+* `deprecationNotice?: { disabled: boolean, warning: () => LocalizedString, experiment?: string }`: Deprecation notice.
+* `learnMore?: LearnMore`: Help link or tooltip info.

package/.agents/skills/gerrit-cli/SKILL.md

@@ -0,0 +1,59 @@
+---
+name: gerrit-cli
+description: >-
+  Interacts with the public Gerrit Code Review platform using depot_tools'
+  gerrit_client.py. Use this skill when asked to query public CLs, retrieve
+  file revisions, add patchset comments, vote on review labels, submit changes,
+  or abandon/restore public CLs. Do not use this skill for Google-internal
+  attention set updates or internal AI-assisted code reviews (CRUAS) which are
+  unsupported by the public API.
+---
+
+# Gerrit CLI Skill
+
+Execute public Gerrit Code Review commands using `gerrit_client.py` from
+depot_tools.
+
+## Prerequisites
+
+- **Environment**: Always execute the wrapper script using **`vpython3`** instead of `python3` to ensure all internal dependencies are satisfied.
+
+- Ensure `gerrit_client.py` is available in the system `PATH` (typically part of
+  `depot_tools`). If `gerrit_client.py` is not available in your environment,
+  stop execution immediately.
+- Use the wrapper script directly instead of an environment variable.
+  Substitute:
+  `vpython3 .agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py`
+  as the executable command in all examples and invocations.
+
+## Just-in-Time (JiT) Loading Guidance
+
+- Before running any Gerrit CLI command, read `references/commands.md`
+  to locate the required parameters and specific subcommand syntax.
+- Before querying public CLs, adding comments, voting, or submitting changes,
+  read `references/workflows.md` for step-by-step procedures.
+
+## Global Flags
+
+The wrapper script includes DevTools-specific defaults for `--host` and
+`--project`. You do not need to provide them unless you are targeting a
+different host or project.
+
+- **Default Host**: `https://chromium-review.googlesource.com`
+- **Default Project**: `devtools/devtools-frontend`
+- **JSON Output**: Always use the `--json_file=<path>` flag when querying
+  changes or fetching metadata to obtain structured, machine-readable output.
+
+> [!CAUTION]
+> **NEVER** use this to add patchset comments to an existing comment thread that
+> contains human reviewers in it. Using an agent to reply to a human is a
+> violation of Chromium's code of conduct.
+>
+> If the user requests this or you encounter this scenario as part of your work,
+> inform the user about which comment threads cannot be updated but otherwise
+> continue work.
+
+
+> [!NOTE]
+> This skill was adapted from the [Chromium Gerrit CLI skill](https://chromium.googlesource.com/chromium/agents/+/main/skills/gerrit-cli/)
+> (automatically rolled in from upstream).

package/.agents/skills/gerrit-cli/references/commands.md

@@ -0,0 +1,93 @@
+# Gerrit CLI Common Commands & Usage (Public)
+
+Run the tool directly using the wrapper script path with the `--help` flag:
+- `vpython3 .agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py --help`
+- `vpython3 .agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py changes --help`
+
+## Global Flags
+
+Use the following global flags for all commands:
+
+- `--host <url>` (e.g., `--host https://chromium-review.googlesource.com`).
+- `--project <project_name>` (e.g., `--project chromium/src`).
+- `--json_file <path>` (saves the structured response as a JSON file).
+
+______________________________________________________________________
+
+## Common Invocations
+
+### 1. Inspecting and Searching Changes
+
+- **Query active changes:**
+  ```bash
+  vpython3 .agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py \
+    changes \
+    --query "owner:self status:open"
+  ```
+- **View the content of a specific file in a change:**
+  ```bash
+  vpython3 .agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py \
+    content \
+    --json_file output.json \
+    --change <change_id> --revision <revision> --path <file_path>
+  ```
+- **Get related changes:**
+  ```bash
+  vpython3 .agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py \
+    relatedchanges \
+    --change <change_id> --revision <revision>
+  ```
+
+### 2. Reviewing and Voting
+
+- **Add a patchset-level comment:**
+  ```bash
+  vpython3 .agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py \
+    addpatchsetcomment \
+    --change <change_id> --revision <revision> \
+    --message "Review findings: <message>"
+  ```
+- **Vote on a review label (e.g., Code-Review +1):**
+  ```bash
+  vpython3 .agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py \
+    setlabel \
+    --change <change_id> \
+    --label Code-Review 1
+  ```
+
+### 3. Actions and Shepherding
+
+- **Submit/Merge a change:**
+  ```bash
+  vpython3 .agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py \
+    submitchange \
+    --change <change_id>
+  ```
+- **Abandon a change:**
+  ```bash
+  vpython3 .agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py \
+    abandon \
+    --change <change_id> \
+    --message "<reason>"
+  ```
+- **Restore an abandoned change:**
+  ```bash
+  vpython3 .agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py \
+    restore \
+    --change <change_id> \
+    --message "<reason>"
+  ```
+
+______________________________________________________________________
+
+## Just-in-Time Help
+
+Explore the built-in CLI help for additional subcommands or advanced syntax:
+
+- Display all top-level commands:
+  `vpython3 .agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py --help`
+- Display help for a specific subcommand:
+  ```bash
+  vpython3 .agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py \
+    help <command>
+  ```

package/.agents/skills/gerrit-cli/references/workflows.md

@@ -0,0 +1,56 @@
+# Gerrit CLI Workflows (Public)
+
+## 1. Change List Review Workflow
+
+Execute these steps in chronological order to review a Change List (CL) when
+provided with a link or ID:
+
+1. **Query CL Metadata**: Retrieve CL details and verify its current status:
+   ```bash
+   vpython3 .agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py \
+     changes \
+     --query "change:<id>"
+   ```
+2. **Fetch File Contents**: Retrieve the content of specific files modified in
+   the CL:
+   ```bash
+   vpython3 .agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py \
+     content \
+     --change <change_id> --revision current --path <file_path>
+   ```
+3. **Analyze Local Modifications**: Inspect the fetched contents and local diffs
+   for any logic or formatting issues.
+4. **Add Review Comment**: Post a patchset-level comment containing the review
+   findings:
+   ```bash
+   vpython3 .agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py \
+     addpatchsetcomment \
+     --change <change_id> --revision current \
+     --message "Review findings: ..."
+   ```
+
+## 2. Shepherding & Submission Workflow
+
+Execute these steps in chronological order to approve and merge a Change List:
+
+1. **Check Related Changes**: Retrieve the status of all related changes to
+   ensure there are no unresolved blockers:
+   ```bash
+   vpython3 .agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py \
+     relatedchanges \
+     --change <change_id> --revision current
+   ```
+2. **Vote on Review Labels**: Apply the required Code-Review approval vote:
+   ```bash
+   vpython3 .agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py \
+     setlabel \
+     --change <change_id> \
+     --label Code-Review 1
+   ```
+3. **Submit Change**: Merge the change once all CQ presubmits pass and all
+   approval requirements are satisfied:
+   ```bash
+   vpython3 .agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py \
+     submitchange \
+     --change <change_id>
+   ```

package/.agents/skills/gerrit-cli/scripts/gerrit_client_wrapper.py

@@ -0,0 +1,47 @@
+#!/usr/bin/env python3
+# Copyright 2026 The Chromium Authors
+# Use of this source code is governed by a BSD-style license that can be
+# found in the LICENSE file.
+"""Helper wrapper script to run gerrit_client.py from PATH."""
+
+import shutil
+import subprocess
+import sys
+
+
+def main():
+    client = shutil.which('gerrit_client.py')
+    if not client:
+        print('gerrit_client.py not found. '
+              'Is depot_tools available and added to PATH?')
+        sys.exit(1)
+
+    # DevTools specific defaults
+    default_args = [
+        '--host',
+        'https://chromium-review.googlesource.com',
+        '--project',
+        'devtools/devtools-frontend',
+    ]
+
+    # gerrit_client.py expects: <command> [options] [args]
+    # We need to extract the command from sys.argv and put it first.
+    user_args = sys.argv[1:]
+    command = []
+    other_args = []
+    for i, arg in enumerate(user_args):
+        if not arg.startswith('-'):
+            command = [arg]
+            other_args = user_args[:i] + user_args[i + 1:]
+            break
+    else:
+        other_args = user_args
+
+    full_args = command + default_args + other_args
+
+    rc = subprocess.call(['vpython3', client] + full_args)
+    sys.exit(rc)
+
+
+if __name__ == '__main__':
+    main()