Ansible Pull Request Review
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.
Final self-review before opening or updating a Saleor pull request: pre-commit, local tests, schema regeneration and a correctly placed CHANGELOG entry.
Install Saleor PR Checklist
$ npx skills add saleor/saleor --skill saleor-pr-checklist -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install saleor/saleor saleor-pr-checklist --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/saleor/saleor.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/saleor-pr-checklist .claude/skills/saleor-pr-checklist && 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 "saleor-pr-checklist" agent skill from https://github.com/saleor/saleor/tree/main/.claude/skills/saleor-pr-checklist into .claude/skills/saleor-pr-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "saleor-pr-checklist", 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/saleor/saleor/tree/main/.claude/skills/saleor-pr-checklistType 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 saleor/saleor --skill saleor-pr-checklist -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install saleor/saleor saleor-pr-checklist --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/saleor/saleor.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/saleor-pr-checklist .agents/skills/saleor-pr-checklist && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "saleor-pr-checklist" agent skill from https://github.com/saleor/saleor/tree/main/.claude/skills/saleor-pr-checklist into .agents/skills/saleor-pr-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "saleor-pr-checklist", 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 saleor/saleor --skill saleor-pr-checklist -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install saleor/saleor saleor-pr-checklist --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/saleor/saleor.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/saleor-pr-checklist .cursor/skills/saleor-pr-checklist && 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 "saleor-pr-checklist" agent skill from https://github.com/saleor/saleor/tree/main/.claude/skills/saleor-pr-checklist into .cursor/skills/saleor-pr-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "saleor-pr-checklist", 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/saleor/saleor.git --path .claude/skills/saleor-pr-checklist--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 saleor/saleor --skill saleor-pr-checklist -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install saleor/saleor saleor-pr-checklist --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/saleor/saleor.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/saleor-pr-checklist .gemini/skills/saleor-pr-checklist && 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 "saleor-pr-checklist" agent skill from https://github.com/saleor/saleor/tree/main/.claude/skills/saleor-pr-checklist into .gemini/skills/saleor-pr-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "saleor-pr-checklist", 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 saleor/saleor saleor-pr-checklistInstalls 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 saleor/saleor --skill saleor-pr-checklist -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/saleor/saleor.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/saleor-pr-checklist .github/skills/saleor-pr-checklist && 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 "saleor-pr-checklist" agent skill from https://github.com/saleor/saleor/tree/main/.claude/skills/saleor-pr-checklist into .github/skills/saleor-pr-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "saleor-pr-checklist", 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 saleor/saleor --skill saleor-pr-checklist -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install saleor/saleor saleor-pr-checklist --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/saleor/saleor.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/saleor-pr-checklist .opencode/skills/saleor-pr-checklist && 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 "saleor-pr-checklist" agent skill from https://github.com/saleor/saleor/tree/main/.claude/skills/saleor-pr-checklist into .opencode/skills/saleor-pr-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "saleor-pr-checklist", 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
saleor-pr-checklist- GitHub stars
- 23k
- Token cost
- ~778 tokens
- SKILL.md length
- 388 words
- Files
- 1
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- BSD-3-Clause
At a glance
Final self-review before opening or updating a Saleor pull request: pre-commit, local tests, schema regeneration and a correctly placed CHANGELOG entry.
- Finishing a change to Saleor and about to request review
- SKILL.md covers Process gate, CHANGELOG, Self-review against the… and PR description
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Checking a PR for the hygiene issues reviewers flag most often
What it does
This is a pre-review gate for the Saleor commerce API. It runs pre-commit and fixes everything flagged (formatting, lint, mypy), checks that new or changed tests pass locally, removes leftover debug code such as stray casts, prints and unused imports, regenerates schema.graphql when the GraphQL schema changed, and for dependency bumps uses the pinned uv version while touching only the target dependency so uv.lock does not churn unrelated entries.
For the changelog, the entry goes under the correct existing section or heading rather than appended to the end of the file, and an entry is never added or edited for a version that has already been released. For schema-specific or migration-specific work, the skill points to the separate saleor-graphql-api-change and saleor-migrations skills.
When your agent uses it
- Finishing a change to Saleor and about to request review
- Checking a PR for the hygiene issues reviewers flag most often
- Adding a CHANGELOG entry for an unreleased change
Example prompts
- “I'm about to open this PR; run the checklist and fix anything it flags.”
- “Did I add the CHANGELOG entry in the right section before this release?”
- “Check if the GraphQL schema needs regenerating before I request review.”
Requirements
- A Saleor checkout with pre-commit and uv configured
What it can do on your machine
Read from SKILL.md and the folder at commit 782a751. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Saleor PR Checklist loads about 778 tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 388 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 saleor/saleor at commit 782a751, republished under its BSD-3-Clause licence (© saleor). 388 words, ~778 tokens.
Download SKILL.mdSave it as
.claude/skills/saleor-pr-checklist/SKILL.md (or your agent's skills folder).- name
- saleor-pr-checklist
- description
- Final self-review gate before opening or updating a Saleor pull request — CHANGELOG placement, pre-commit, schema regen, and a pass over the review standards that reviewers most often enforce. Use when finishing a change and about to request review.
Saleor PR checklist
Run this before opening or updating a PR. It catches the process/hygiene issues and the recurring
review comments that otherwise cost a round trip. (For schema-specific and migration-specific work,
also use saleor-graphql-api-change and saleor-migrations.)
Process gate
- Run pre-commit and fix everything it flags (formatting, lint, mypy). PRs regularly bounce for this alone.
- Ensure new/changed tests pass locally before requesting review (see AGENTS.md for how to run tests).
- Remove debug/test scaffolding (stray
str(...)casts, prints, unused imports). - If you touched the GraphQL schema, regenerate
schema.graphql. - For dependency changes, use the pinned
uvversion and change only the target dependency souv.lockdoesn't churn.
CHANGELOG
- Add an entry under the correct section/heading — don't blind-append to the end of the file.
- Never add or edit a CHANGELOG entry for an already-released version. Released fixes surface via the release description; a re-added entry is noise. (This is a frequent porting mistake.)
- Keep the changelog diff scoped to your change — don't drop unrelated entries. Proofread the prose.
- Add a migration-guide entry for any behavior change that could be breaking for some API consumers, even one intended as a feature.
Show full SKILL.md (201 more words)Show less
Self-review against the standards reviewers enforce
Skim your own diff for the top recurring review comments (all detailed in AGENTS.md):
- Tests: exact-value assertions (no
> 0/assert not errors); negative tests assert the side effect didn't happen; no asserting a value the test just set; design tests so a shared input can't mutate the expected value, rather than papering over it with an expensivecopy.deepcopy; real fixtures over mocked internals; the fix has a regression test reproducing the real bug. - Layering: business logic in the domain layer, not the mutation; no
graphql-layer imports from non-GraphQL code; validate at the point of production. - DB / scaling: no N+1 in loops; bulk
update/delete; only-needed columns;on_commitfor task scheduling; no blocking in request threads. - Naming: no cryptic abbreviations; positive booleans;
legacy_prefix on deprecated-behavior flags. - Error handling: specific exceptions (not bare
Exception); retryable vs terminal distinguished; precise, field-attributed messages. - Dead code / types: delete code a refactor made dead; fix types at the source instead of
cast().
PR description
- Explain why, and for anything non-obvious (a deprecation path, a deferred cleanup, a concurrency decision) state it explicitly so a reviewer doesn't have to ask.
- Link tracked follow-up issues for any deferred work (column drops, legacy removals).
© saleor, BSD-3-Clause. 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/saleor-pr-checklist of saleor/saleor.
Open the folder on GitHubat commit 782a751
Compare with similar skills
Saleor PR Checklist 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 |
|---|---|---|---|---|---|---|
| Saleor PR Checklist this skillsaleor/saleor | 23k | — | ~778 | Automated safety check: Pass | BSD-3-Clause | |
| Ansible Pull Request Reviewansible/ansible | 71k | — | ~570 | Automated safety check: Pass | GPL-3.0 | |
| Code ReviewAzure/Azurite | 2.3k | — | ~734 | Automated safety check: Pass | MIT | |
| Address PR Review Commentscashew-labs/libretto | 904 | — | ~532 | Automated safety check: Pass | MIT | |
| 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 |
Similar skills
- Official
Code Review
Azure/Azurite
Review Azurite pull requests with service-aware checks for Blob, Queue, and Table behavior, API compatibility, tests, and release notes.
Address PR Review Comments
cashew-labs/libretto
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.
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.
More from saleor/saleor
All 8 skills in this repoDjango Filter Benchmark
saleor/saleor
Benchmarks Django ORM filters in Saleor by generating bulk data, extracting the SQL and running EXPLAIN ANALYZE to check index usage.
Saleor Commit Workflow
saleor/saleor
Commits changes in the Saleor codebase and works through pre-commit hook failures from ruff, mypy, the GraphQL schema check and the migrations check.
Saleor Django Schema Migration
saleor/saleor
Generates and splits Django schema migrations for Saleor with manage.py makemigrations, enforcing one new model or one field change per migration file.
Saleor Django Migration Rules
saleor/saleor
Rules for writing Django migrations in Saleor that avoid long table locks and stay compatible with zero-downtime rolling deploys.
Pytest Runner
saleor/saleor
Run pytest tests with automatic virtual environment activation. Use this skill whenever running tests, executing pytest, or when asked to "run tests", "test…
Saleor Port Changes
saleor/saleor
Forward-ports or backports a single PR or branch onto the currently checked-out Saleor branch, handling GraphQL version markers and migration numbering along the way.
Related
Works with
Categories
Questions about Saleor PR Checklist
What does Saleor PR Checklist do?
Final self-review before opening or updating a Saleor pull request: pre-commit, local tests, schema regeneration and a correctly placed CHANGELOG entry. This is a pre-review gate for the Saleor commerce API.lock does not churn unrelated entries.
When should I use Saleor PR Checklist?
Saleor PR Checklist fits situations like: finishing a change to Saleor and about to request review; checking a PR for the hygiene issues reviewers flag most often; adding a CHANGELOG entry for an unreleased change.
How do I install Saleor PR Checklist in Claude Code?
Run `npx skills add saleor/saleor --skill saleor-pr-checklist -a claude-code`. Or copy the skill folder (.claude/skills/saleor-pr-checklist in saleor/saleor) into .claude/skills/saleor-pr-checklist in your project. Claude Code loads it when a task matches its description.
How do I install Saleor PR Checklist in Codex?
Run `npx skills add saleor/saleor --skill saleor-pr-checklist -a codex`. Or copy the skill folder (.claude/skills/saleor-pr-checklist in saleor/saleor) into .agents/skills/saleor-pr-checklist in your project. Codex loads it when a task matches its description.
Can I use Saleor PR Checklist 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 saleor/saleor --skill saleor-pr-checklist -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/saleor-pr-checklist, .gemini/skills/saleor-pr-checklist, .github/skills/saleor-pr-checklist and .opencode/skills/saleor-pr-checklist in your project.
What does Saleor PR Checklist need to run?
SKILL.md names no scripts, command-line tools or credentials: Saleor PR Checklist is instructions for the agent only. Our summary lists: A Saleor checkout with pre-commit and uv configured.
Does Saleor PR Checklist access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Saleor PR Checklist 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 Saleor PR Checklist use?
Saleor PR Checklist is published under the BSD-3-Clause licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Saleor PR Checklist use?
About 778 tokens (SKILL.md is roughly 3.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 Saleor PR Checklist?
Skills that share tags, products or a category with Saleor PR Checklist: Ansible Pull Request Review (ansible/ansible, 71k stars), Code Review (Azure/Azurite, 2.3k stars), Address PR Review Comments (cashew-labs/libretto, 904 stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Saleor PR Checklist?
saleor (a GitHub organization) maintains it in saleor/saleor, which has 23,428 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 9, 2026.
Source: saleor/saleor on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.