Builds and deploys UI demos/mocks for the ChromeOS Fleet Console/Milo UI to Google App Engine (GAE) for development and demo purposes. Handles GAE version naming constraints, VPC/cache permission workarounds, and ensures workspace cleanup after deployment.

2026-07-16159

prepare-cl

luci/luci-go

Verifies, commits, and uploads code changes as a Gerrit CL. Use when you have completed a task, fixed a bug, or are ready to submit changes for review.

2026-07-16159

frontend-performance-optimization

luci/luci-go

Guidelines, metrics, testing patterns, and referential stability standards for measuring and vetting frontend performance optimizations in the LUCI Fleet Console. Use this skill when refactoring React hooks, tuning custom data fetching hooks (e.g., using TanStack Query), stabilizing component re-renders, or writing robust Cypress tests for tables.

2026-06-11159

manual-testing

luci/luci-go

Instructions for manually testing the Fleet Console using the browser subagent. Use when you need to verify UI changes, filter interactions, or page loads in the actual browser.

2026-06-11159

authoring-skills

luci/luci-go

Guides the creation, editing, formatting, and structural best practices for agentic skills. Use this skill when writing or reviewing skill markdown files.

2026-06-08159

coordinating-multiple-repositories

luci/luci-go

Coordinates commit order, branch safety, and submodule updates in workspaces containing nested git repositories. Use this skill when editing code or checking status across parent and submodule boundaries.

2026-06-08159

name	gerrit-workflows
description	Guidelines and commands for managing stacked CLs, preserving review votes, and querying Gerrit API.

Gerrit Workflows Skill

This skill guides the agent in managing Gerrit CL stacks, preserving review votes, and querying Gerrit metadata efficiently.

Workflow

[!IMPORTANT] At the start of a task involving Gerrit CLs, you MUST copy the progress checklist below into your very next response to the user, and check off the steps sequentially as you complete them.

Progress:

Step 1: Request persistent git command permissions
Step 2: Configure branch upstream tracking and issue mapping
Step 3: Fetch and rebase parent and child branches correctly
Step 4: Verify changes do not modify files not already present in the CL's diff (if addressing comments on a +1 CL to preserve votes)
Step 5: Upload parent CL from parent branch
Step 6: Upload downstream CL from child branch

1. Preserving Review Votes (Gerrit +1)

[!IMPORTANT] Uploading any new patchset to a CL will reset its Gerrit Code-Review votes.

If a reviewer has already granted Code-Review+1 and requests non-trivial changes, do not upload a new patchset to that CL unless you want to discard the +1 vote.

Instead, address the feedback in a new downstream CL parented on the original CL to maintain review velocity.

2. Managing & Uploading CL Stacks

When working with stacked CLs (e.g., CL B depends on CL A), configure git upstream branch tracking:
```
# While on branch CL-B:
git branch --set-upstream-to=CL-A-branch
```
Rebasing Stacked Branches: When a parent branch (CL-A) is rebased or amended, a simple git rebase CL-A-branch on the child branch (CL-B) can trigger merge conflicts because git tries to re-apply the old parent commits. To rebase safely, use one of the following methods:

Method A: git rebase-update (Recommended) This depot_tools utility automatically and cleanly rebases all local stacked branches on their respective upstreams:
```
git rebase-update
```
Method B: Explicit Rebase Onto If you need to rebase manually, specify the boundary to skip the old parent commits:
```
# While on CL-B-branch:
git rebase --onto CL-A-branch <old-CL-A-commit>
```
where <old-CL-A-commit> is the commit hash of the parent CL before it was rebased/amended. If conflicts arise during rebase:
1. Resolve conflicts in the files.
2. Stage the resolved files: git add <files>
3. Continue rebase: git rebase --continue (never create new commits during rebase).
Linking to an Existing CL: If a branch has already been uploaded but lost its association, link it to the issue:
```
git cl issue <issue_number>
```
How to Upload Stacked CLs: To prevent Gerrit from getting confused about relation chains:
1. Checkout the parent branch (CL A).
2. Run upload: git cl upload -f --commit-description=+
3. Checkout the child branch (CL B).
4. Run upload: git cl upload -f --commit-description=+
Cleaning Up Accumulating Commits (Unstacking & Decoupling Branches): When rebasing local branches that were previously stacked, a branch may carry over commits and file modifications from its old parent branches, causing git cl upload to pull in unrelated changes. To surgically clean up a branch so it contains exactly one commit with only the desired changes:
1. Checkout origin/main to a temporary branch:
```
git checkout -b temp-clean-branch origin/main
```
2. Checkout only the files belonging to the specific CL from your dirty local branch:
```
git checkout <dirty-branch-name> -- path/to/file1.tsx path/to/file2.ts
```
3. Commit the clean files:
```
git commit -m "[Category] Commit description message"
```
4. Switch back to your dirty branch and hard reset it to the clean state:
```
git checkout <dirty-branch-name> && git reset --hard temp-clean-branch
```
5. Delete the temporary branch:
```
git branch -D temp-clean-branch
```
This guarantees the branch contains exactly one commit on top of origin/main with no unrelated tracking files.

3. Preserving Git Rename Tracking & License Header Hygiene

Preserve Rename Tracking (R vs A): When moving or renaming source or test files, keep the file's inner content as close to the original as possible (aim for >90% similarity index) in the renaming commit. This ensures Git's rename detection tracks the history correctly as a Rename (R) rather than an Addition (A) and Deletion (D), which simplifies code reviews and prevents PRESUBMIT.py (CheckLicense) from enforcing new-file rules.
Separate Renames from Refactoring: Avoid introducing heavy structural refactoring in the same commit as the file move. Perform renames in a dedicated commit first, then apply clean refactoring in subsequent commits.
Tiered Copyright Header / Presubmit Governance (CheckLicense): When touching or renaming existing/legacy code files (*_OLD.tsx, *_deprecated.go), if PRESUBMIT.py (CheckLicense) fails on older copyright dates or header formatting, follow this strict tiered hierarchy:
1. Tier 1 (Git Rename Tracking): Ensure the commit cleanly tracks the rename (R). If Git recognizes the rename or simple modification (M), standard Chromium/LUCI presubmits accept any historical year from 2011 to the current year (2026).
2. Tier 2 (Update Copyright Header / Year): If a first-party file is flagged by CheckLicense (e.g., due to strict new-file checks on renames or malformed header syntax), update the copyright header or bump the year to 2026 (// Copyright 2026 The Chromium Authors). Bringing first-party code headers into compliance is standard, best-practice engineering hygiene.
3. Tier 3 (Last Resort — Bypass-Check-License): Only append Bypass-Check-License: <reason> to the commit description footer if working with external third-party vendor code or imported files where modifying copyright statements is strictly restricted by licensing terms. Never use Bypass-Check-License as a default or shortcut on first-party Chromium/LUCI files.

4. Querying Gerrit API (CLI Efficiency)

Do not use browser sessions or browser subagents to fetch Gerrit metadata. Instead, use the authenticated Gerrit REST API with curl using the --netrc flag (to load credentials from ~/.netrc) and the /a/ prefix.

[!NOTE] The examples below use the standard host chromium-review.googlesource.com. Adjust the domain accordingly if the repository is configured for a different Gerrit host.

Retrieve Related Changes (Relation Chain):

curl -s --netrc "https://chromium-review.googlesource.com/a/changes/<issue_number>/revisions/current/related" | tail -n +2 | jq .

Retrieve CL Detail:

curl -s --netrc "https://chromium-review.googlesource.com/a/changes/<issue_number>/detail" | tail -n +2 | jq .

[!NOTE] The tail -n +2 is required to strip Gerrit's anti-XSS magic prefix ()]}') from the beginning of the JSON response, ensuring JSON parsers (or jq) do not fail.

[!WARNING] If a curl call returns a 401 Unauthorized or redirect page, verify that ~/.netrc contains valid credentials for chromium-review.googlesource.com. If missing or expired, ask the user to regenerate their password at https://chromium-review.googlesource.com/new-password.

5. Requesting Git Permissions

At the start of any session involving git operations, request persistent prefix permission for the git command using the ask_permission tool:

Action: command
Target: git This allows stack management and uploads to run without repeatedly prompting the user.

6. Change-Id Lifecycle & Superproject Submodule Safety

Change-Id Lifecycle on Initial Commits vs Amends (invalid Change-Id prevention): When committing a brand new branch (git checkout -b <branch> origin/main), never hardcode or copy a Change-Id: from a scratch file or earlier commit description. Omit Change-Id: entirely from your initial commit message file (-F) so that Gerrit's commit-msg hook generates a unique SHA-1 hash (Change-Id: I...). Only include or preserve Change-Id: when amending (--amend) an already uploaded CL to maintain Patchset continuity.
Preventing Accidental Submodule Staging in Superprojects (infra/infra): When operating inside superprojects (infra/infra), do NOT run git commit -a or git add -A, as this automatically stages local commit pointers for git submodules (luci, go/src/go.chromium.org/...) and causes Gerrit upload rejections (unexpected git links). Always stage specific target file paths (git add path/to/file.go), verify with git status --short, and recover polluted submodules using git reset HEAD <submodule_path> (git checkout HEAD -- <submodule_path>) or running gclient sync before running git cl upload.