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

Ansible Pull Request Review

by ansible in ansible/ansible

Reviews an Ansible pull request by number, following the steps in the project's CLAUDE.md, with early checks for changelog fragments and tests.

GPL-3.0Auto-check passedDevelopment

Install Ansible Pull Request Review

skills CLI
$ npx skills add ansible/ansible --skill review -a claude-code

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

GitHub CLI
$ gh skill install ansible/ansible 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/ansible/ansible.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/review .claude/skills/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
review
GitHub stars
71k
Token cost
~570 tokens
SKILL.md length
245 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
GPL-3.0

At a glance

Reviews an Ansible pull request by number, following the steps in the project's CLAUDE.md, with early checks for changelog fragments and tests.

  • Works in 8 steps: Create TodoWrite list for systematic… → Get PR details: gh pr view to understand… → Get PR diff: gh pr diff to see all changes → …
  • Reviewing an incoming pull request against the Ansible repository
  • Calls gh
  • Verifying that a PR has a changelog fragment in the correct section

What it does

The command takes a single GitHub pull request number and works through a fixed list of review steps tracked in a TodoWrite list. It reads the PR details and diff with the `gh` CLI, checks out the branch, and reads existing comments and bot results so that unresolved feedback can be named explicitly.

Required components come first: a changelog fragment in `changelogs/fragments/` placed in a section allowed by `changelogs/config.yaml`, and tests that exercise the changed code. Unit tests should be pytest style and functional rather than tied to mocks, and plugin changes almost always need integration tests. The review also checks that new dependencies fit the GPLv3 and BSD-2-Clause licensing, and a single review round should stay under 20 feedback items.

When your agent uses it

  • Reviewing an incoming pull request against the Ansible repository
  • Verifying that a PR has a changelog fragment in the correct section
  • Checking that new tests actually cover the changed code paths
  • Summarizing which reviewer comments on a PR are still unresolved

Example prompts

  • “Run the review command on the pull request I am about to merge.”
  • “Review this Ansible plugin PR and tell me if the integration tests are missing.”
  • “Check whether any reviewer feedback on this PR is still open.”

Requirements

  • GitHub CLI (`gh`) with access to the repository
  • A checkout of the Ansible repository with its CLAUDE.md
  • Pre-approved tools (allowed-tools): TodoWrite, Bash(gh pr view:*), Bash(gh pr diff:*), Bash(gh pr checkout:*), Bash(gh pr checks:*), Read, Grep, Glob, Search

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Create TodoWrite list for systematic review tracking
  2. Get PR details: gh pr view to understand scope, motivation and the desired outcome
  3. Get PR diff: gh pr diff to see all changes
  4. Check required components FIRST
  5. Checkout PR branch: gh pr checkout to examine code holistically
  6. Review existing feedback: gh pr view --comments for all comments and previous reviews
  7. Verify all issues addressed: Ensure bot failures, reviewer requests, and discussion points are resolved
  8. Call out unresolved feedback: Explicitly mention any discussions/requests that remain unaddressed

What it can do on your machine

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

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • TodoWrite
    • Bash(gh pr view:*)
    • Bash(gh pr diff:*)
    • Bash(gh pr checkout:*)
    • Bash(gh pr checks:*)
    • Read
    • Grep
    • Glob
    • Search

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh

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

  • Network

    No URLs in SKILL.md. Its commands use gh, 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

Ansible Pull Request Review loads about 570 tokens when it runs. Until then it costs about 22 tokens; SKILL.md has 245 words of instructions outside code blocks.

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

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 ansible/ansible at commit 5b1a96f, republished under its GPL-3.0 licence (© ansible). 245 words, ~570 tokens.

Download SKILL.mdSave it as .claude/skills/review/SKILL.md (or your agent's skills folder).
name
review
description
Review an Ansible PR following the project's standardized process from CLAUDE.md
allowed-tools
TodoWrite, Bash(gh pr view:*), Bash(gh pr diff:*), Bash(gh pr checkout:*), Bash(gh pr checks:*), Read, Grep, Glob, Search
argument-hint
<pr_number>
user-invocable
true

PR Review Command

Review an Ansible PR following the project's standardized process from CLAUDE.md.

Usage

bash
/review <pr_number>

Arguments

  • pr_number (required): The GitHub PR number to review

Implementation

This command implements the PR Review Guidelines documented in the PR Review Guidelines section of CLAUDE.md.

Review Process Steps

The command follows these numbered steps from CLAUDE.md:

  1. Create TodoWrite list for systematic review tracking
  2. Get PR details: gh pr view <number> to understand scope, motivation and the desired outcome
  3. Get PR diff: gh pr diff <number> to see all changes
  4. Check required components FIRST:
    • Verify changelog fragment exists in changelogs/fragments/
    • Verify changelog uses correct section (check changelogs/config.yaml)
    • Verify tests exist and specifically cover the changed code paths
    • Unit tests should be pytest style, and functional rather than tightly coupled to mocking
    • Integration tests required for almost all plugin changes
  5. Checkout PR branch: gh pr checkout <number> to examine code holistically
  6. Review existing feedback: gh pr view <number> --comments for all comments and previous reviews
  7. Verify all issues addressed: Ensure bot failures, reviewer requests, and discussion points are resolved
  8. Call out unresolved feedback: Explicitly mention any discussions/requests that remain unaddressed

Critical Review Elements

  • Licensing: Verify GPLv3/BSD-2-Clause compatibility for any new dependencies
  • Test scope: Tests must exercise actual changed code, not just add random coverage
  • Changelog validation: Fragment structure follows sections defined in changelogs/config.yaml

Each step is tracked in TodoWrite for visibility and systematic completion. A review round should not exceed 20 feedback items.

© ansible, GPL-3.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 .claude/skills/review of ansible/ansible.

Open the folder on GitHubat commit 5b1a96f

Compare with similar skills

Ansible Pull Request 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.

Ansible Pull Request Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Ansible Pull Request Review this skillansible/ansible71k—~570Automated safety check: PassGPL-3.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
GitHub Review Iterationprisma/orm48k—~2.2kAutomated safety check: PassApache-2.0
PR Review State Fetchprisma/orm48k—~767Automated safety check: PassApache-2.0
PR Finalize Reviewmicrosoft/garnet12k—~3.1kAutomated safety check: PassMIT
Fastlane Pull Request Reviewfastlane/fastlane42k—~550Automated safety check: PassMIT

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

  • GitHub Review Iteration

    prisma/orm

    Official

    Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.

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

  • PR Review State Fetch

    prisma/orm

    Official

    Fetches a pull request's canonical review state as JSON, validates it, and renders markdown, a text summary and triage target files from it using bundled scripts.

    48k GitHub stars~767 tokensUpdated today
    DevelopmentAuto-check passed

  • PR Finalize Review

    microsoft/garnet

    Official

    Checks that a pull request's title and description match its implementation and reviews the code for Garnet best practices, reporting findings without posting them.

    12k GitHub stars~3.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Fastlane Pull Request Review

    fastlane/fastlane

    Reviews a fastlane pull request against its linked issue and the project guides, separating blocking from non-blocking findings and handling vulnerabilities privately.

    42k GitHub stars~550 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Pull Request Babysitter

    thedotmack/claude-mem

    Keeps watching a pull request, fixing real review and CI problems and resolving stale threads, until it is clean and ready to merge.

    99k GitHub stars~1.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from ansible/ansible

  • Ansible Development Context

    ansible/ansible

    Load Ansible project development guidelines, testing conventions, PR review processes, and code structure reference into context

    71k GitHub stars~427 tokensUpdated yesterday
    Auto-check passed

  • Azure Pipelines Log Downloader

    ansible/ansible

    Downloads Azure Pipelines CI logs for an Ansible pull request or build so the agent can analyze test failures, after asking you first.

    71k GitHub stars~825 tokensUpdated yesterday
    Auto-check passed

  • Ansible Backport Creator

    ansible/ansible

    Creates backports of a merged Ansible devel pull request onto the right stable branches by cherry-picking its merge commit onto new backport branches.

    71k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Ansible Pull Request Review

What does Ansible Pull Request Review do?

Reviews an Ansible pull request by number, following the steps in the project's CLAUDE.md, with early checks for changelog fragments and tests. The command takes a single GitHub pull request number and works through a fixed list of review steps tracked in a TodoWrite list. It reads the PR details and diff with the `gh` CLI, checks out the branch, and reads existing comments and bot results so that unresolved feedback can be named explicitly.

When should I use Ansible Pull Request Review?

Ansible Pull Request Review fits situations like: reviewing an incoming pull request against the Ansible repository; verifying that a PR has a changelog fragment in the correct section; checking that new tests actually cover the changed code paths; summarizing which reviewer comments on a PR are still unresolved.

How do I install Ansible Pull Request Review in Claude Code?

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

How do I install Ansible Pull Request Review in Codex?

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

Can I use Ansible Pull Request 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 ansible/ansible --skill 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/review, .gemini/skills/review, .github/skills/review and .opencode/skills/review in your project.

What does Ansible Pull Request Review need to run?

Going by SKILL.md and its folder, Ansible Pull Request Review needs the command-line tools its instructions call (gh). Our summary lists: GitHub CLI (`gh`) with access to the repository; A checkout of the Ansible repository with its CLAUDE.md. Its frontmatter pre-approves these tools: TodoWrite, Bash(gh pr view:*), Bash(gh pr diff:*), Bash(gh pr checkout:*), Bash(gh pr checks:*), Read, Grep, Glob, Search.

Does Ansible Pull Request Review access the network?

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

Is Ansible Pull Request 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 Ansible Pull Request Review use?

Ansible Pull Request Review is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Ansible Pull Request Review use?

About 570 tokens (SKILL.md is roughly 2.3k 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 Ansible Pull Request Review?

Skills that share tags, products or a category with Ansible Pull Request Review: PR Babysitter (openinterpreter/openinterpreter, 69k stars), GitHub Review Iteration (prisma/orm, 48k stars), PR Review State Fetch (prisma/orm, 48k stars) and PR Finalize Review (microsoft/garnet, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ansible Pull Request Review?

ansible (a GitHub organization) maintains it in ansible/ansible, which has 70,893 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 8, 2026.

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