Agent skill · writing content · google
adk-bot-review
Reviews adk-bot pull requests by validating technical correctness against source code, checking PR states and formatting, and following Google's developer documentation style and ADK docs conventions. Triggers on "review bot PR", "check bot changes", or "verify bot issue".
Why this skill is useful
Provides detailed guidelines for validating adk-bot PRs, ensuring adherence to specific documentation standards and conventions not commonly known.
What it needs
About 4k tokens when loaded. Last updated 2026-08-07. 1,462 stars on the source repository.
What this skill does
Review changes proposed by adk-bot (adk-bot-review) This skill guides a rigorous review of adk-bot changes. It ensures documentation updates are technically accurate, appropriately sized, and follow ADK docs conventions, based on Google's developer documentation style. Step 1: Verify and research the proposed adk-bot change Check that the PR title briefly describes the topic being updated, not only the issue. Confirm changes are made directly in the .md files and no "do not merge" status tags were prematurely removed. Check the PR's mergeable state and CI status. Note git conflicts and failing checks as findings to resolve or to fix in the consolidating PR. The input is one adk-bot-authored PR, or occasionally a few. From the PR, trace back to the issue and the specific item it addresses. Identify the item from the PR title ("Update ADK doc according to issue #<N> - <item>") and body. adk-bot often opens more than one PR for the same item. If multiple PRs are provided, confirm they all address the same item and review them together as one consolidation set. If they address different items, ask the user which one to focus on before continuing. Search closed issues and merged/rejected PRs across the repository for similar topics. Ensure the bot is not re-introducing changes, APIs, or stylistic choices that human maintainers have previously debated and rejected. Summarize the item's intended change and stated reasoning, and carry that intent into the technical validation in the next steps. Step 2: Assess update criteria and architecture Prioritize smaller, surgical updates over comprehensive overhauls unless the existing docs are entirely unclear. Verify that the update provides a useful learning experience and is actionable for a developer. Ensure the content is placed appropriately within the ADK docs information architecture. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills google/adk-bot-review