Agent skill

Address Review

by druxt in druxt/druxt.js

Works through review comments and failing CI on a druxt.js pull request, fixing or answering each one until the pull request is green and every thread has a reply.

MITAuto-check passedDevelopment

Install Address Review

skills CLI
$ npx skills add druxt/druxt.js --skill address-review -a claude-code

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

GitHub CLI
$ gh skill install druxt/druxt.js address-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/druxt/druxt.js.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/address-review .claude/skills/address-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
address-review
GitHub stars
114
Token cost
~600 tokens
SKILL.md length
333 words
Files
2
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

Works through review comments and failing CI on a druxt.js pull request, fixing or answering each one until the pull request is green and every thread has a reply.

  • Works in 4 steps: Collect everything open → Fix CI first → Answer every comment → …
  • A druxt.js pull request has review comments
  • SKILL.md covers 1. Collect everything open, 2. Fix CI first, 3. Answer every comment and 4. Push and re-verify
  • Calls gh and git

What it does

Address Review is an agent skill from druxt/druxt.js. Works through review comments and failing CI on a druxt.js pull request, fixing or answering each one until the pull request is green and every thread has a reply. Use when a druxt.js pull request has review comments, requested changes, bot findings or a failing check, including a request to re-run CI until it passes.

Its SKILL.md is about 600 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `evals/tests.yaml`).

It sits in Development, covering Pull requests. The repository describes itself as: The Fully Decoupled Drupal Framework. The licence is MIT.

When your agent uses it

  • A druxt.js pull request has review comments
  • Requested changes
  • A failing check
  • Including a request to re-run CI until it passes

Example prompts

  • “Use the address-review skill to work through review comments and failing CI on a druxt.js pull request, fixing or answering each one until the pull…”
  • “/address-review”

Workflow steps

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

  1. Collect everything open
  2. Fix CI first
  3. Answer every comment
  4. Push and re-verify

What it can do on your machine

Read from SKILL.md and the folder at commit 93c48da. 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:

    • gh
    • git

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

  • Network

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

Address Review loads about 600 tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 333 words of instructions outside code blocks.

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

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 druxt/druxt.js at commit 93c48da, republished under its MIT licence (© druxt). 333 words, ~600 tokens.

Download SKILL.mdSave it as .claude/skills/address-review/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
address-review
description
Works through review comments and failing CI on a druxt.js pull request, fixing or answering each one until the pull request is green and every thread has a reply. Use when a druxt.js pull request has review comments, requested changes, bot findings or a failing check, including a request to re-run CI until it passes.

Address review

A pull request is ready to merge when CI is green on its latest commit and every review thread has an answer. Work through both.

1. Collect everything open

bash
gh pr view <number> --repo druxt/druxt.js --comments
gh pr checks <number> --repo druxt/druxt.js
gh api repos/druxt/druxt.js/pulls/<number>/comments --paginate

gh pr view shows review summaries but not inline review comments, so the gh api call lists those, replies included. Read every inline comment, review summary, bot finding and failing check. A finding from a bot is a bug report like any other.

2. Fix CI first

For each failing check, reproduce it locally with the same command CI runs (the verify-change skill lists them), find the cause and fix it. When a test fails because of a behaviour change in a commit you didn't write, read the whole commit message and ask its author whether the change is meant to happen before you touch the test. Until they answer, treat the code as the thing to fix. Re-running a job until it passes is not a fix. If the check also fails on develop, say so on the pull request with the evidence and leave it to the maintainers.

3. Answer every comment

For each comment:

  1. Check the claim against the code before changing anything. Reviewers can be wrong, and so can you.
  2. If it is correct and small (a rename, a missing test, a clearer @param), fix it.
  3. If it asks for a larger change (a new API, a refactor across packages, a design change), reply with a proposal and wait for the reviewer.
  4. If it is wrong, reply with the reason and the evidence.

Reply on the thread itself, naming the commit that fixes it. Draft the replies and post them when the person you work for asks you to.

4. Push and re-verify

Add new commits on top of the branch, so reviewers can see what changed since their review. Re-run the verify-change gate, push, then ask the reviewer to look again.

bash
git push origin <branch>

Repeat until CI is green and no thread is waiting on you.

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

Files

SKILL.md and 1 other file in .agents/skills/address-review of druxt/druxt.js.

  • SKILL.md
  • evals/tests.yaml

Open the folder on GitHubat commit 93c48da

Compare with similar skills

Address 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.

Address Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Address Review this skilldruxt/druxt.js114—~600Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
PR Design DocOpenHands/OpenHands90k—~2.4kAutomated safety check: PassMIT
WooCommerce Code Reviewwoocommerce/woocommerce11k3 repos~1.1kAutomated safety check: PassCustom licence

Similar skills

  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • 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
  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed
  • PR Design Doc

    OpenHands/OpenHands

    For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…

    90k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed
  • WooCommerce Code Review

    woocommerce/woocommerce

    Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.

    11k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Record PR Demo

    payloadcms/payload

    A skill your agent uses when a Payload pull request needs a concise visual walkthrough for reviewers.

    45k GitHub stars~1k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from druxt/druxt.js

  • Add Changeset

    druxt/druxt.js

    Writes the changeset that versions a druxt.js package change and becomes its changelog entry.

    114 GitHub stars~763 tokensUpdated today
    Auto-check passed
  • Open PR

    druxt/druxt.js

    Prepares and opens a druxt.js pull request from a contributor's fork against develop, with a Conventional Commits title and the repository's template filled in.

    114 GitHub stars~771 tokensUpdated today
    Auto-check passed
  • Start Work

    druxt/druxt.js

    Sets up a druxt.js change before the first edit, from the issue to a feature branch off develop, a short spec and a failing test.

    114 GitHub stars~887 tokensUpdated today
    Auto-check passed
  • Triage Issue

    druxt/druxt.js

    Sorts a druxt.js issue by type and package, and reproduces it against the example Drupal backend or with a failing unit test before writing up the findings.

    114 GitHub stars~763 tokensUpdated today
    Auto-check passed
  • Verify Change

    druxt/druxt.js

    Runs the druxt.js verification gate (lint, build, unit tests and the checks for whatever else changed) and reports the real results.

    114 GitHub stars~916 tokensUpdated today
    Auto-check passed
  • Write Skill

    druxt/druxt.js

    Creates or changes a druxt.js contributor skill in .agents/skills, with its evals and the tests that gate it.

    114 GitHub stars~926 tokensUpdated today
    Auto-check passed

Categories

Questions about Address Review

What does Address Review do?

Works through review comments and failing CI on a druxt.js pull request, fixing or answering each one until the pull request is green and every thread has a reply. js.js pull request, fixing or answering each one until the pull request is green and every thread has a reply.

When should I use Address Review?

Address Review fits situations like: A druxt.js pull request has review comments; requested changes; A failing check; including a request to re-run CI until it passes.

How do I install Address Review in Claude Code?

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

How do I install Address Review in Codex?

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

Can I use Address 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 druxt/druxt.js --skill address-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/address-review, .gemini/skills/address-review, .github/skills/address-review and .opencode/skills/address-review in your project.

What does Address Review need to run?

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

Does Address Review access the network?

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

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

Address 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 Address Review use?

About 600 tokens (SKILL.md is roughly 2.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 Address Review?

Skills that share tags, products or a category with Address Review: Finishing a Development Branch (obra/superpowers, 297k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and PR Design Doc (OpenHands/OpenHands, 90k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Address Review?

druxt (a GitHub organization) maintains it in druxt/druxt.js, which has 114 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 9, 2026.

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