chromium: Command for Gemini CLI

.gemini/commands/cr/git/pre-upload-checklist.toml

pre-upload-checklist is a command for Gemini CLI from chromium/chromium. It costs 0 tokens per session (632 once invoked), scanned A, original, BSD-3-Clause.

A checklist command for reviewing a code changelist before upload, including dependency sync, changed-file inspection, style checks, and removal of temporary debug logging.

In plain words
What is it for?
Use it to prepare a branch for upload by checking dependencies, comparing changes with the upstream branch, reading the project style guide, and checking for debug logs.
Why use it?
It catches common quality and presubmit problems before code is uploaded for review.

Command for Gemini CLI

Written for Gemini CLI: installed under .gemini/.

This is chromium/chromium's own configuration. It tells Gemini CLI how to work on chromium itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything chromium configures →

About the project

Chromium is an open-source web browser project and the official GitHub mirror of its source code. It is used to build and maintain software for browsing the web, with documentation and code for products such as Chrome and Android WebView.

chromium/chromium · 24,735 stars · on GitHub · chromium.googlesource.com

Reuse

Borrowing it

Nothing to install: this file belongs to chromium/chromium. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/chromium/chromium/main/.gemini/commands/cr/git/pre-upload-checklist.toml
Clone the repo
git clone --depth 1 https://github.com/chromium/chromium

Made for: Gemini CLI.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for pre-upload-checklist

README.md
[![agentmods](https://agentmods.dev/badge/commands/chromium/chromium/pre-upload-checklist.svg)](https://agentmods.dev/commands/chromium/chromium/pre-upload-checklist)
Your own site
<a href="https://agentmods.dev/commands/chromium/chromium/pre-upload-checklist"><img src="https://agentmods.dev/badge/commands/chromium/chromium/pre-upload-checklist.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 632 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00632
Opus 5 $0.00000 $0.00316
Sonnet 5 $0.00000 $0.00126
Haiku 4.5 $0.00000 $0.00063

Measured 6d ago against content hash 0e6d7bee636a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

pre-upload-checklist scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.gemini/commands/cr/git/pre-upload-checklist.toml · 69 lines

How it starts

The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.

description = """Runs a pre-upload checklist to ensure the changelist is in a high-quality, presubmit-clean state."""

prompt = """

🚀 Pre-Upload Checklist Prompt

Philosophy: The goal of this checklist is to perform a thorough manual and automated local review, ensuring the changelist is in a high-quality, presubmit-clean state before you decide whether to proceed with optional actions like building or uploading.


Part 1: Mandatory Pre-Upload Checks

1. Sync Client First, I will run gclient sync to ensure all dependencies are up to date.

2. Identify Changed Files Next, I will identify the files that have been modified on the current branch by running the following command: git diff --name-only @{u}

3. Review Style Guide and Current Changes I will read the style guide at @styleguide/styleguide.md in its entirety. I will then analyze the changed files identified in the previous step to ensure they adhere to the project's coding standards. I will report any violations before proceeding.

4. Remove Debug Logging I will analyze the diff of the changed files to find and remove any temporary logging statements, such as System.out.println or Log.d, that may have been accidentally left in the code.

5. Add Missing Docstrings I will then analyze the full diff of the changes to identify any new or modified classes, methods, or functions that lack proper documentation. For each of these, I will:

  • Write a clear and concise docstring explaining the code's purpose, parameters, and return values.
  • Ensure the documentation style conforms to the relevant language-specific guidelines (e.g., JavaDoc for Java).

6. Run Presubmit Checks As a final local verification, I will run git cl presubmit. This is a comprehensive check to ensure the changelist is free of errors before proceeding. This step is mandatory, and I will report on its success or failure.


Read the full file on GitHub · 69 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 6d ago First seen · 69 lines · 0 tokens per session scan A 0e6d7bee636a

Subscribe to this mod's changes

pre-upload-checklist is a command published in the GitHub repository chromium/chromium (24,735 stars, last pushed today), licensed BSD-3-Clause. It costs nothing until one of its globs matches a file; then it loads 632 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-02.