Saleor PR Checklist
saleor/saleor
Final self-review before opening or updating a Saleor pull request: pre-commit, local tests, schema regeneration and a correctly placed CHANGELOG entry.
Works through the review comments on a pull request one by one: fetches the threads, makes the fixes, runs type-check, build and lint, pushes, and resolves the threads.
Install Address PR Review Comments
$ npx skills add cashew-labs/libretto --skill address-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cashew-labs/libretto address-review --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/cashew-labs/libretto.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/address-review .claude/skills/address-review && rm -rf skills-srcUse ~/.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/
Install the "address-review" agent skill from https://github.com/cashew-labs/libretto/tree/main/.agents/skills/address-review into .claude/skills/address-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "address-review", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/cashew-labs/libretto/tree/main/.agents/skills/address-reviewType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add cashew-labs/libretto --skill address-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cashew-labs/libretto address-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cashew-labs/libretto.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/address-review .agents/skills/address-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "address-review" agent skill from https://github.com/cashew-labs/libretto/tree/main/.agents/skills/address-review into .agents/skills/address-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "address-review", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cashew-labs/libretto --skill address-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cashew-labs/libretto address-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cashew-labs/libretto.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/address-review .cursor/skills/address-review && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "address-review" agent skill from https://github.com/cashew-labs/libretto/tree/main/.agents/skills/address-review into .cursor/skills/address-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "address-review", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/cashew-labs/libretto.git --path .agents/skills/address-review--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add cashew-labs/libretto --skill address-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cashew-labs/libretto address-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cashew-labs/libretto.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/address-review .gemini/skills/address-review && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "address-review" agent skill from https://github.com/cashew-labs/libretto/tree/main/.agents/skills/address-review into .gemini/skills/address-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "address-review", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install cashew-labs/libretto address-reviewInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add cashew-labs/libretto --skill address-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cashew-labs/libretto.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/address-review .github/skills/address-review && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "address-review" agent skill from https://github.com/cashew-labs/libretto/tree/main/.agents/skills/address-review into .github/skills/address-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "address-review", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cashew-labs/libretto --skill address-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cashew-labs/libretto address-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cashew-labs/libretto.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/address-review .opencode/skills/address-review && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "address-review" agent skill from https://github.com/cashew-labs/libretto/tree/main/.agents/skills/address-review into .opencode/skills/address-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "address-review", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
address-review- GitHub stars
- 904
- Token cost
- ~532 tokens
- SKILL.md length
- 226 words
- Files
- 1
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- MIT
At a glance
Works through the review comments on a pull request one by one: fetches the threads, makes the fixes, runs type-check, build and lint, pushes, and resolves the threads.
- Works in 6 steps: Get review comments: Use gh api graphql… → Analyze comments: Review all the… → Address each comment systematically: For… → …
- Responding to code review feedback on a pull request
- SKILL.md covers Process, Implementation Pattern and Notes
- Calls gh
What it does
The agent fetches all review threads and comments for the PR with `gh api graphql`, looking up the PR for the current branch when no number is given, and reads the feedback to see what must change. For each comment it makes the requested change, verifies that the change fixes the issue, adds an explanatory comment if the reviewer asked for clarification, and tests that nothing existing breaks.
It then runs type-check, build and lint, commits and pushes, and marks the addressed threads resolved through a GraphQL `resolveReviewThread` mutation, always resolving outdated ones. The notes limit it to reviews from human users unless bot reviews are requested, suggest sub-agents for independent comments in parallel, and say to stick to the issues raised instead of making extra changes.
When your agent uses it
- Responding to code review feedback on a pull request
- Clearing every open review thread before asking for another review
- Resolving outdated review threads on a PR
Example prompts
- “Address the review comments on the PR for my current branch.”
- “Fix everything the reviewers asked for on this pull request, then resolve the threads.”
- “Handle the open review threads on my PR and push the fixes.”
Requirements
- GitHub CLI (`gh`) authenticated for the repository
- The project's type-check, build and lint commands
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Get review comments: Use gh api graphql to fetch all review threads and comments for the PR. (If a PR number is not provided in the input…
- Analyze comments: Review all the feedback to understand what changes are needed
- Address each comment systematically: For each review comment
- Quality assurance: Run type-check, build, and lint to ensure all changes are correct
- Commit and push: Stage and commit all changes with an appropriate message and push.
- Mark comments resolved: Query PR review threads with gh api graphql to get thread IDs and outdated status. Resolve all addressed threads…
What it can do on your machine
Read from SKILL.md and the folder at commit 41ab782. 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
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
Address PR Review Comments loads about 532 tokens when it runs. Until then it costs about 30 tokens; SKILL.md has 226 words of instructions outside code blocks.
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 cashew-labs/libretto at commit 41ab782, republished under its MIT licence (© cashew-labs). 226 words, ~532 tokens.
Download SKILL.mdSave it as
.claude/skills/address-review/SKILL.md (or your agent's skills folder).- name
- address-review
- description
- Address PR review comments systematically. Use when responding to code review feedback on a pull request.
Address PR review comments systematically.
Process
Get review comments: Use
gh api graphqlto fetch all review threads and comments for the PR. (If a PR number is not provided in the input, look up the PR for the current branch).Analyze comments: Review all the feedback to understand what changes are needed
Address each comment systematically: For each review comment:
- Make the requested code changes
- Verify the changes fix the issue raised
- Add explanatory comments if the reviewer requested clarification
- Test changes to ensure they don't break existing functionality
Quality assurance: Run type-check, build, and lint to ensure all changes are correct
Commit and push: Stage and commit all changes with an appropriate message and push.
Mark comments resolved: Query PR review threads with
gh api graphqlto get thread IDs and outdated status. Resolve all addressed threads usingmutation { resolveReviewThread(input: {threadId: "THREAD_ID"}) { thread { isResolved } } }. Always resolve outdated threads.
Implementation Pattern
// Query review threads:
gh api graphql -f query='query { repository(owner: "owner", name: "repo") { pullRequest(number: N) { reviewThreads(first: 100) { nodes { id isResolved isOutdated comments { nodes { body } } } } } } }'
// Resolve thread:
gh api graphql -f query='mutation { resolveReviewThread(input: {threadId: "THREAD_ID"}) { thread { isResolved } } }'Notes
- Only address reviews from human users; ignore bot reviews (e.g., Claude) unless explicitly requested
- Use sub-agents to handle independent review comments in parallel when possible
- Always verify changes don't introduce new issues
- If a review comment requires clarification, document the approach taken
- Focus on the specific issues raised rather than making additional changes
- Mark outdated comments as resolved automatically since they no longer apply to current code
© cashew-labs, 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 .agents/skills/address-review of cashew-labs/libretto.
Open the folder on GitHubat commit 41ab782
Compare with similar skills
Address PR Review Comments 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Address PR Review Comments this skillcashew-labs/libretto | 904 | — | ~532 | Automated safety check: Pass | MIT | |
| Saleor PR Checklistsaleor/saleor | 23k | — | ~778 | Automated safety check: Pass | BSD-3-Clause | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| WooCommerce Code Reviewwoocommerce/woocommerce | 11k | 3 repos | ~1.1k | Automated safety check: Pass | Custom licence | |
| Open Code Review CLIalibaba/open-code-review | 46k | — | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| GitHub Review Iterationprisma/orm | 48k | — | ~2.2k | Automated safety check: Pass | Apache-2.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.
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.
Open Code Review CLI
alibaba/open-code-review
Runs the ocr command-line tool to review Git changes, a commit or a branch comparison with an AI model, returning line-level comments and optionally applying fixes.
- Official
GitHub Review Iteration
prisma/orm
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.
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.
More from cashew-labs/libretto
All 21 skills in this repoSystem Prompt Writing Guide
cashew-labs/libretto
Lays out a minimal, iteration-first approach to writing system prompts for LLM agents, with model-specific notes for Claude, GPT, Gemini, and Codex.
CLI Development
cashew-labs/libretto
Design rules for command-line tools: subcommand-scoped help, actionable success output, debuggable failures, stable output, meaningful exit codes and a --json mode.
External Electron App Automation
cashew-labs/libretto
Drives desktop Electron apps already installed on your machine, such as Slack, Discord or VS Code, by relaunching them with a debugging port and using the Libretto CLI.
Merge Conflict Resolver
cashew-labs/libretto
Resolves Git merge, rebase and cherry-pick conflicts by reading the PRs behind each side, keeping both intents and asking you when they truly clash.
Feature Spec Generator
cashew-labs/libretto
Researches the codebase and relevant docs, asks clarifying questions, then writes a spec sheet in specs/ for a significant feature or complex fix.
Glimpse Changes Walkthrough
cashew-labs/libretto
Turns the current session's code changes into a Markdown walkthrough shown in a native Glimpse window, with highlighted code, rendered diffs and review feedback.
Related
Works with
Categories
Questions about Address PR Review Comments
What does Address PR Review Comments do?
Works through the review comments on a pull request one by one: fetches the threads, makes the fixes, runs type-check, build and lint, pushes, and resolves the threads. The agent fetches all review threads and comments for the PR with `gh api graphql`, looking up the PR for the current branch when no number is given, and reads the feedback to see what must change. For each comment it makes the requested change, verifies that the change fixes the issue, adds an explanatory comment if the reviewer asked for clarification, and tests that nothing existing breaks.
When should I use Address PR Review Comments?
Address PR Review Comments fits situations like: responding to code review feedback on a pull request; clearing every open review thread before asking for another review; resolving outdated review threads on a PR.
How do I install Address PR Review Comments in Claude Code?
Run `npx skills add cashew-labs/libretto --skill address-review -a claude-code`. Or copy the skill folder (.agents/skills/address-review in cashew-labs/libretto) into .claude/skills/address-review in your project. Claude Code loads it when a task matches its description.
How do I install Address PR Review Comments in Codex?
Run `npx skills add cashew-labs/libretto --skill address-review -a codex`. Or copy the skill folder (.agents/skills/address-review in cashew-labs/libretto) into .agents/skills/address-review in your project. Codex loads it when a task matches its description.
Can I use Address PR Review Comments 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 cashew-labs/libretto --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 PR Review Comments need to run?
Going by SKILL.md and its folder, Address PR Review Comments needs the command-line tools its instructions call (gh). Our summary lists: GitHub CLI (`gh`) authenticated for the repository; The project's type-check, build and lint commands.
Does Address PR Review Comments 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 Address PR Review Comments 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 PR Review Comments use?
Address PR Review Comments 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 PR Review Comments use?
About 532 tokens (SKILL.md is roughly 2.1k 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 PR Review Comments?
Skills that share tags, products or a category with Address PR Review Comments: Saleor PR Checklist (saleor/saleor, 23k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), WooCommerce Code Review (woocommerce/woocommerce, 11k stars) and Open Code Review CLI (alibaba/open-code-review, 46k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Address PR Review Comments?
cashew-labs (a GitHub organization) maintains it in cashew-labs/libretto, which has 904 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on August 21, 2026.
Source: cashew-labs/libretto on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.