New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Gerrit Review

by ambient-code in ambient-code/platform

A skill your agent uses when reviewing a Gerrit change — fetching change details, reading diffs, posting inline comments, and voting with labels.

MITAuto-check passedDevelopment

Install Gerrit Review

skills CLI
$ npx skills add ambient-code/platform --skill gerrit-review -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ambient-code/platform gerrit-review --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ambient-code/platform.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/plugins/gerrit-skills/skills/gerrit-review .claude/skills/gerrit-review && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
gerrit-review
GitHub stars
131
Token cost
~846 tokens
SKILL.md length
420 words
Files
1
Skills in repo
18
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when reviewing a Gerrit change — fetching change details, reading diffs, posting inline comments, and voting with labels.

  • Works in 4 steps: Fetch the change → Read the diffs → Analyze and form review feedback → …
  • Reviewing a Gerrit change — fetching change details
  • SKILL.md covers Prerequisites, Workflow and Error handling
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Gerrit Review is an agent skill from ambient-code/platform. Use when reviewing a Gerrit change — fetching change details, reading diffs, posting inline comments, and voting with labels. Triggers on "review this Gerrit change", "review change 12345", "look at this Gerrit CL", "code review on Gerrit".

Its SKILL.md is about 850 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Code review and Technical documentation. It works with Model Context Protocol. The repository describes itself as: Vision/Mission https://ambient-code.ai : Virtual team management and collaboration platform. User guides: https://ambient-code.github.io/platform/. The licence is MIT.

When your agent uses it

  • Reviewing a Gerrit change — fetching change details
  • Posting inline comments
  • Voting with labels
  • Review this Gerrit change

Example prompts

  • “review this Gerrit change”
  • “review change 12345”
  • “look at this Gerrit CL”
  • “/gerrit-review”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Fetch the change
  2. Read the diffs
  3. Analyze and form review feedback
  4. Post the review

What it can do on your machine

Read from SKILL.md and the folder at commit 57e8af8. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Gerrit Review loads about 846 tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 420 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~64
When it runs · the whole SKILL.md, loaded when a task matches
~846

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from ambient-code/platform at commit 57e8af8, republished under its MIT licence (© ambient-code). 420 words, ~846 tokens.

Download SKILL.mdSave it as .claude/skills/gerrit-review/SKILL.md (or your agent's skills folder).
name
gerrit-review
description
Use when reviewing a Gerrit change — fetching change details, reading diffs, posting inline comments, and voting with labels. Triggers on "review this Gerrit change", "review change 12345", "look at this Gerrit CL", "code review on Gerrit".

Gerrit Code Review

Guide for reviewing changes on a Gerrit instance using the Gerrit MCP server tools.

Prerequisites

The Gerrit MCP server must be available (credentials configured via Integrations page). If mcp__gerrit__* tools are not listed, the user needs to connect their Gerrit instance first.

Workflow

1. Fetch the change

Use mcp__gerrit__fetch_gerrit_change with the change ID (numeric or change-Id).

Extract from the response:

  • Subject and commit message — understand what the change does
  • Owner — who authored it
  • Status — NEW (open), MERGED, ABANDONED
  • Current patch set number — the latest revision
  • Files changed — list of modified files with insertions/deletions
  • Existing comments — what reviewers have already said
  • Labels — current votes (Code-Review, Verified, etc.)
2. Read the diffs

Use mcp__gerrit__fetch_patchset_diff to compare patch sets or view the current diff.

  • To see the full change: compare patch set 1 vs current (or base vs current)
  • To see what changed between review rounds: compare two specific patch sets
  • Filter by file path if the change is large — focus on the most impactful files first
3. Analyze and form review feedback

Apply standard code review principles:

  • Correctness — does the logic do what the commit message claims?
  • Edge cases — missing null checks, boundary conditions, error handling
  • Style — follows project conventions (check CLAUDE.md if available)
  • Security — no credentials in code, proper input validation, no injection vectors
  • Performance — unnecessary allocations, N+1 queries, missing caching
Show full SKILL.md (197 more words)Show less
4. Post the review

Use mcp__gerrit__submit_gerrit_review to post feedback:

  • message: A summary of your review findings (top-level comment)
  • labels: Vote appropriately:
    • Code-Review +1 — looks good but someone else should also review
    • Code-Review +2 — approved, ready to submit (only if you have authority)
    • Code-Review -1 — needs changes before merging
    • Code-Review -2 — blocks submission (serious issues)
    • Verified +1 — tests pass, builds clean
  • comments: Inline comments on specific files and lines
Gerrit conventions
  • Attention set: After reviewing, the change owner gets added to the attention set automatically. Don't manually manage attention set unless needed.
  • Patchset iteration: When the owner uploads a new patch set addressing your comments, re-review by comparing the previous and new patch sets (fetch_patchset_diff), not re-reading the entire change.
  • Resolved comments: In Gerrit, comments can be marked as "resolved" or "unresolved". Focus on unresolved comments when re-reviewing.
  • Vote semantics: Code-Review -2 is a hard block — use it only for architectural issues or security problems, not style nits.

Error handling

  • If the change ID is not found, verify the instance name and change number
  • If authentication fails, suggest the user reconnect via the Integrations page
  • If the MCP server is not available, check that Gerrit credentials are configured

© ambient-code, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/plugins/gerrit-skills/skills/gerrit-review of ambient-code/platform.

Open the folder on GitHubat commit 57e8af8

Compare with similar skills

Gerrit Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Gerrit Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Gerrit Review this skillambient-code/platform131—~846Automated safety check: PassMIT
Library Documentation Seekerwithkynam/vibecode-pro-max-kit1.1k2 repos~1kAutomated safety check: NotesMIT
Change Verification Gatefengshao1227/ccg-workflow5.9k—~511Automated safety check: NotesMIT
Post Draft Reviewagent-substrate/substrate4.5k—~2.8kAutomated safety check: PassApache-2.0
Graph-Based Change Reviewtirth8205/code-review-graph32k1 repos~331Automated safety check: PassMIT
YugabyteDB Backport Reviewyugabyte/yugabyte-db11k—~2.5kAutomated safety check: PassCustom licence

Similar skills

  • Library Documentation Seeker

    withkynam/vibecode-pro-max-kit

    Looks up library and framework documentation through Context7 first, with bundled Node scripts as a fallback that fetch and analyze llms.txt files.

    1.1k GitHub starsUsed in 2 repos~1k tokens
    DevelopmentAuto-check: notes

  • Change Verification Gate

    fengshao1227/ccg-workflow

    Analyzes a code diff for documentation sync, test coverage and impact scope, warning when docs or tests lag behind a design-level change or a large edit.

    5.9k GitHub stars~511 tokensUpdated 22 days ago
    DevelopmentAuto-check: notes

  • Post Draft Review

    agent-substrate/substrate

    Posts pull request review findings as GitHub draft (pending) inline comments for a human to edit and submit, instead of publishing them straight to the PR author.

    4.5k GitHub stars~2.8k tokensUpdated today
    DevelopmentAuto-check passed

  • Graph-Based Change Review

    tirth8205/code-review-graph

    Reviews a change set using a code knowledge graph for risk scores, blast radius and test gaps, and ends with a merge recommendation.

    32k GitHub starsUsed in 1 repo~331 tokens
    DevelopmentAuto-check passed

  • YugabyteDB Backport Review

    yugabyte/yugabyte-db

    Checks a YugabyteDB backport revision on Phorge against the original diff it was ported from and flags differences, tracing unexplained code back to master.

    11k GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check passed

  • Liveagent Code Review

    Stack-Cairn/LiveAgent

    Review an open GitHub pull request or the current local branch and working tree with parallel, independent reviewers and evidence-based validation.

    2.2k GitHub stars~2k tokensUpdated today
    DevelopmentAuto-check passed

More from ambient-code/platform

All 18 skills in this repo

  • Align

    ambient-code/platform

    Run a convention alignment check across the codebase to measure adherence to documented standards.

    131 GitHub stars~754 tokensUpdated today
    Auto-check passed

  • Amber Review

    ambient-code/platform

    Perform a comprehensive code review using repository-specific standards.

    131 GitHub stars~1.4k tokensUpdated today
    Auto-check passed

  • Cypress Demo

    ambient-code/platform

    Create a Cypress-based video demo for a feature branch with cursor, click effects, and captions.

    131 GitHub stars~879 tokensUpdated today
    Auto-check: notes

  • Deploy

    ambient-code/platform

    Deploy, update manifests, and troubleshoot the ambient-ui component.

    131 GitHub stars~2.6k tokensUpdated today
    Auto-check passed

  • Discover

    ambient-code/platform

    Discover domain-specific skills and context before starting any coding or spec work.

    131 GitHub stars~747 tokensUpdated today
    Auto-check passed

  • Frontend Development

    ambient-code/platform

    Required context for all frontend work. An agent skill from ambient-code/platform.

    131 GitHub stars~525 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Gerrit Review

What does Gerrit Review do?

A skill your agent uses when reviewing a Gerrit change — fetching change details, reading diffs, posting inline comments, and voting with labels. Gerrit Review is an agent skill from ambient-code/platform. Use when reviewing a Gerrit change — fetching change details, reading diffs, posting inline comments, and voting with labels.

When should I use Gerrit Review?

Gerrit Review fits situations like: reviewing a Gerrit change — fetching change details; posting inline comments; voting with labels; review this Gerrit change.

How do I install Gerrit Review in Claude Code?

Run `npx skills add ambient-code/platform --skill gerrit-review -a claude-code`. Or copy the skill folder (.claude/plugins/gerrit-skills/skills/gerrit-review in ambient-code/platform) into .claude/skills/gerrit-review in your project. Claude Code loads it when a task matches its description.

How do I install Gerrit Review in Codex?

Run `npx skills add ambient-code/platform --skill gerrit-review -a codex`. Or copy the skill folder (.claude/plugins/gerrit-skills/skills/gerrit-review in ambient-code/platform) into .agents/skills/gerrit-review in your project. Codex loads it when a task matches its description.

Can I use Gerrit Review in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ambient-code/platform --skill gerrit-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gerrit-review, .gemini/skills/gerrit-review, .github/skills/gerrit-review and .opencode/skills/gerrit-review in your project.

What does Gerrit Review need to run?

SKILL.md names no scripts, command-line tools or credentials: Gerrit Review is instructions for the agent only.

Does Gerrit Review access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Gerrit Review safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Gerrit Review use?

Gerrit Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Gerrit Review use?

About 846 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Gerrit Review?

Skills that share tags, products or a category with Gerrit Review: Library Documentation Seeker (withkynam/vibecode-pro-max-kit, 1.1k stars), Change Verification Gate (fengshao1227/ccg-workflow, 5.9k stars), Post Draft Review (agent-substrate/substrate, 4.5k stars) and Graph-Based Change Review (tirth8205/code-review-graph, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Gerrit Review?

ambient-code (a GitHub organization) maintains it in ambient-code/platform, which has 131 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 7, 2026.

Source: ambient-code/platform on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.