New: 97,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

Official agent skill

Review Changes

by docker in docker/docs

Review uncommitted or recently committed documentation changes for correctness, coherence, and style compliance.

OfficialApache-2.0Auto-check passedDevelopment

Install Review Changes

skills CLI
$ npx skills add docker/docs --skill review-changes -a claude-code

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

GitHub CLI
$ gh skill install docker/docs review-changes --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/docker/docs.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/review-changes .claude/skills/review-changes && 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
review-changes
GitHub stars
4.7k
Token cost
~845 tokens
SKILL.md length
428 words
Files
1
Skills in repo
13
Repo updated
First seen
Licence
Apache-2.0

At a glance

Review uncommitted or recently committed documentation changes for correctness, coherence, and style compliance.

  • Works in 7 steps: Identify what changed → Read each changed file in full → Follow cross-references → …
  • Tasks that involve Code review
  • SKILL.md covers 1. Identify what changed, 2. Read each changed file in…, 3. Follow cross-references and 4. Verify factual accuracy, plus 3 more sections
  • Calls git

What it does

Review Changes is an agent skill from docker/docs, published by the product's own GitHub organization. Review uncommitted or recently committed documentation changes for correctness, coherence, and style compliance. Use before creating a PR to catch issues. "review my changes", "review the diff", "check the fix before submitting", "does this look right".

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. The repository describes itself as: Source repo for Docker's Documentation. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Code review

Example prompts

  • “review my changes”
  • “review the diff”
  • “check the fix before submitting”
  • “/review-changes”

Workflow steps

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

  1. Identify what changed
  2. Read each changed file in full
  3. Follow cross-references
  4. Verify factual accuracy
  5. Evaluate as a reader
  6. Review code and template changes
  7. Decision

What it can do on your machine

Read from SKILL.md and the folder at commit 65aa5cd. 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

    Shell commands in SKILL.md call:

    • git

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

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    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

Review Changes loads about 845 tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 428 words of instructions outside code blocks.

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

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 docker/docs at commit 65aa5cd, republished under its Apache-2.0 licence (© docker). 428 words, ~845 tokens.

Download SKILL.mdSave it as .claude/skills/review-changes/SKILL.md (or your agent's skills folder).
name
review-changes
description
Review uncommitted or recently committed documentation changes for correctness, coherence, and style compliance. Use before creating a PR to catch issues. "review my changes", "review the diff", "check the fix before submitting", "does this look right".
context
fork
model
opus

Review Changes

Evaluate whether the changes correctly and completely solve the stated problem, without introducing new issues. Start with no assumptions — the change may contain mistakes. Your job is to catch what the writer missed, not to rubber-stamp the diff.

1. Identify what changed

Determine the scope of changes to review:

bash
# Uncommitted changes
git diff --name-only

# Last commit
git diff --name-only HEAD~1

# Entire branch vs main
git diff --name-only main...HEAD

Pick the right comparison for what's being reviewed. If reviewing a branch, use main...HEAD to see all changes since the branch diverged.

2. Read each changed file in full

Do not just read the diff. For every changed file, read the entire file to understand the full context the change lives in. A diff can look correct in isolation but contradict something earlier on the same page.

Then read the diff for the detailed changes:

bash
# Adjust the comparison to match step 1
git diff --unified=10              # uncommitted
git diff --unified=10 HEAD~1       # last commit
git diff --unified=10 main...HEAD  # branch

3. Follow cross-references

For each changed file, check what links to it and what it links to:

  • Search for other pages that reference the changed content (grep for the filename, heading anchors, or key phrases)
  • Read linked pages to verify the change doesn't create contradictions across pages
  • Check that anchor links in cross-references still match heading IDs

A change that's correct on its own page can break the story told by a related page.

4. Verify factual accuracy

Don't assume the change is factually correct just because it reads well.

  • If the change describes how a feature behaves, verify against upstream docs or source code
  • If the change includes a URL, check that it resolves
  • If the change references a CLI flag, option, or API field, confirm it exists
Show full SKILL.md (173 more words)Show less

5. Evaluate as a reader

Consider someone landing on this page from a search result, with no prior context:

  • Does the page make sense on its own?
  • Is the changed section clear without having read the issue or diff?
  • Would a reader be confused by anything the change introduces or leaves out?

6. Review code and template changes

For non-Markdown changes (JS, HTML, CSS, Hugo templates):

  • Trace through the common execution path
  • Trace through at least one edge case (no stored preference, Alpine fails to load, first visit vs returning visitor)
  • Ask whether the change could produce unexpected browser or runtime behavior that no automated tool would catch

7. Decision

Approve if the change is correct, coherent, complete, and factually accurate.

Request changes if:

  • The change does not correctly solve the stated problem
  • There is a factual error or contradiction (on-page or cross-page)
  • A cross-reference is broken or misleading
  • A reader would be confused

When requesting changes, be specific: quote the exact text that is wrong, explain why, and suggest the correct fix.

© docker, Apache-2.0. 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 .agents/skills/review-changes of docker/docs.

Open the folder on GitHubat commit 65aa5cd

Compare with similar skills

Review Changes 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.

Review Changes compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Review Changes this skilldocker/docs4.7k—~845Automated safety check: PassApache-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT
Backend Code Reviewlangflow-ai/langflow156k—~3.5kAutomated safety check: NotesMIT
Understand Diff AnalysisEgonex-AI/Understand-Anything85k1 repos~1.4kAutomated safety check: PassMIT
Mole Bug Patternstw93/Mole69k—~2kAutomated safety check: PassGPL-3.0

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Backend Code Review

    langflow-ai/langflow

    Review backend code for quality, security, maintainability, and best practices based on established checklist rules.

    156k GitHub stars~3.5k tokensUpdated today
    DevelopmentAuto-check: notes

  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    85k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed

  • Mole Bug Patterns

    tw93/Mole

    A catalog of recurring bug shapes in the Mole Mac cleaner, used to review safety-sensitive diffs for deletion safety, unbounded commands, shell traps and weak tests.

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

  • Backend Code Review

    langgenius/dify

    Reviews backend code under api/ for concrete, reproducible defects, routes to rule packs for architecture, schema, repositories and SQLAlchemy, and ranks findings from P0 to P3.

    158k GitHub stars~676 tokensUpdated today
    DevelopmentAuto-check passed

More from docker/docs

All 13 skills in this repo

  • Agent Readiness Audit

    docker/docs

    Official

    Audit a documentation site for agent-friendliness: discovery, markdown delivery, crawlability, semantic structure, machine-readable surfaces, and content legibility.

    4.7k GitHub stars~1.8k tokensUpdated today
    Auto-check passed

  • Migrate Content Ia

    docker/docs

    Official

    Handle Hugo docs information-architecture moves: discover old vs new URLs, add front matter aliases (Phase 1), update in-repo links (Phase 2), interactive List 2 resolution and fragment validation…

    4.7k GitHub stars~5.1k tokensUpdated today
    Auto-check passed

  • Write

    docker/docs

    Official

    Write or edit reader-facing technical prose for immediate comprehension.

    4.7k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Create Lab Guide

    docker/docs

    Official

    Clone a dockersamples Labspace repo, extract learning objectives and module structure from labspace.yaml, and produce a Hugo guide page under content/guides/ with correct frontmatter…

    4.7k GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Curate Whats New

    docker/docs

    Official

    Curate noteworthy Docker launches from documentation pull requests merged during a requested period.

    4.7k GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • Fix Issue

    docker/docs

    Official

    Fix a single GitHub issue end-to-end: triage, research, write the fix, review, and create a PR.

    4.7k GitHub stars~595 tokensUpdated today
    Auto-check passed

Categories

Questions about Review Changes

What does Review Changes do?

Review uncommitted or recently committed documentation changes for correctness, coherence, and style compliance. Review Changes is an agent skill from docker/docs, published by the product's own GitHub organization. Review uncommitted or recently committed documentation changes for correctness, coherence, and style compliance.

When should I use Review Changes?

Review Changes fits situations like: tasks that involve Code review.

How do I install Review Changes in Claude Code?

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

How do I install Review Changes in Codex?

Run `npx skills add docker/docs --skill review-changes -a codex`. Or copy the skill folder (.agents/skills/review-changes in docker/docs) into .agents/skills/review-changes in your project. Codex loads it when a task matches its description.

Can I use Review Changes 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 docker/docs --skill review-changes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/review-changes, .gemini/skills/review-changes, .github/skills/review-changes and .opencode/skills/review-changes in your project.

What does Review Changes need to run?

Going by SKILL.md and its folder, Review Changes needs the command-line tools its instructions call (git).

Does Review Changes access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Review Changes 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 Review Changes use?

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

How many tokens does Review Changes use?

About 845 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 Review Changes?

Skills that share tags, products or a category with Review Changes: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Backend Code Review (langflow-ai/langflow, 156k stars) and Understand Diff Analysis (Egonex-AI/Understand-Anything, 85k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Review Changes?

docker (a GitHub organization, an official publisher) maintains it in docker/docs, which has 4,666 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 7, 2026.

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