saleor-dashboard-pr-quality-check
Skill1.1k starsChanged 8 days agoBSD-3-ClauseView on GitHub
Check a PR (or local branch when no PR is open) against the repo's PR rules — one significant change per PR, a title and description that explain the whole scope, before/after screenshots for UI. Proposes a title and description, offers screenshots and a `gh pr edit` update, and plans a split into smaller PRs with hand-off prompts for other agents. Use when planning work, after each commit, before opening or updating a PR, or when asked to "check the PR", "PR quality", "review PR description", or "should I split this PR".
- Commits and pushes
Trending
Less talk lately.about the whole repository
Who's talking about saleor/saleor-dashboard
- saleor/saleor“Unable to update Company info from Dashboard”GitHub · May 31, 2022 · 2 reactions
- saleor/apps“Implement logo field in AppManifest”GitHub · Feb 22, 2023 · 1 reactions
- saleor/saleor“Support for payment transaction actions”GitHub · Aug 11, 2022 · 1 reactions
- saleor/saleor“feat(attribute): add staff-only internalDescription to Attribute”GitHub · Oct 15, 2026
- waelhe/app-java-v3“docs(admin): plan Saleor Dashboard adaptation for marketplace”GitHub · Oct 15, 2026
The biggest 5 of 50 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 50
Talked about on GitHub (50 times).
On GitHub · 50
- May 31, 2022Unable to update Company info from Dashboard — saleor/saleor2 reactions · 3 comments
- Feb 22, 2023Implement logo field in AppManifest — saleor/apps1 reaction · 3 comments
- Aug 11, 2022Support for payment transaction actions — saleor/saleor1 reaction · 27 comments
- Oct 15, 2026feat(attribute): add staff-only internalDescription to Attribute — saleor/saleor0 reactions · 1 comment
- Oct 15, 2026docs(admin): plan Saleor Dashboard adaptation for marketplace — waelhe/app-java-v30 reactions · 3 comments
45 more on GitHub
- Jul 31, 2026feat(avatax): add tax code action to Dashboard command palette — saleor/apps0 reactions · 5 comments
- Jul 13, 2026Add reason for price override — saleor/saleor0 reactions · 1 comment
- Jul 8, 2026Improved Gift Card APIs — saleor/saleor0 reactions · 1 comment
- Jun 9, 2026[Feature] Support pasting boolean values in other that English — WillSmithTE/saleor-saleor-dashboard0 reactions · 1 comment
- Jun 9, 2026Fix Background task provider tests — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026Missing filter when calling exportGiftCards mutation for selected giftcards — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026Variant view, no scroll on warehouse list and only first 50 warehouses displayed for the user — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: `requestPasswordReset` mutation returns incorrect error when user is not staff user — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026Missed info about no access to the channels — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026 `create order` button should be disabled in case of no permissions — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026User can create group with permission from plugin but cannot assign members via UI — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Enhancement]: Misleading UI when charge is pending — WillSmithTE/saleor-saleor-dashboard0 reactions · 1 comment
- Jun 9, 2026[Bug]: Modal leave without saving after logout — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Feature]: Change navigation structure — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: Only first 50 warehouses are loaded in the grid — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: Weight rate create - not consistent error messages — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: Price rate and weight base availability button inactive — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: Changing attribute value on product triggers SKU fail — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: Restrict order weight in shipping method not saved — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: Datagrids jump to end when resizing column — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026Enable refunding specific product lines — WillSmithTE/saleor-saleor-dashboard0 reactions · 1 comment
- Jun 9, 2026[Bug]: Deleting variant attribute changes variant name — WillSmithTE/saleor-saleor-dashboard0 reactions · 1 comment
- Jun 9, 2026[Bug]: Column picker refinement — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026No information about required fields in product variant form — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026Error handling in product variant page - user can delete required field and still be able to save - then success banner shows up followed by error banner — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: Remove add product — WillSmithTE/saleor-saleor-dashboard0 reactions · 1 comment
- Jun 9, 2026[Bug]: Not all attributes are validated — WillSmithTE/saleor-saleor-dashboard0 reactions · 1 comment
- Jun 9, 2026[Bug]: Error label misplaced — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: Error messages missmatch — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Epic]: Improve UX flow for order refunds using Transactions API — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: Can not refund fulfilled order — WillSmithTE/saleor-saleor-dashboard0 reactions · 1 comment
- Jun 9, 2026[Bug]: Incorrect background in label cell — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: City and Postal code is getting cleared while modifying and saving the country field and country area in warehouse modification — WillSmithTE/saleor-saleor-dashboard0 reactions · 1 comment
- Jun 9, 2026[Bug]:Error displayed while selecting Category name header checkbox and click pagination in category Listing Page — WillSmithTE/saleor-saleor-dashboard0 reactions · 1 comment
- Jun 9, 2026[Bug]: dashboard not using all settings field in query (Can't set limitQuantityPerCheckout) — WillSmithTE/saleor-saleor-dashboard0 reactions · 1 comment
- Jun 3, 2026Add support for editorJS table syntax — saleor/saleor0 reactions · 1 comment
- May 5, 2026HOMEPAGE_WIDGETS types for manifest — saleor/app-sdk0 reactions · 2 comments
- Mar 25, 2026Fix LSP not loading `.js` and `.ts` files correctly — graphql/graphiql0 reactions · 5 comments
- Mar 13, 2026Add proper gift card events when gift card is used as a payment method — saleor/saleor0 reactions · 1 comment
- Mar 12, 2026Fix smoke tests - add prefix for artifact upload — saleor/apps0 reactions · 3 comments
- Mar 6, 2026Introduce password login mode — saleor/saleor0 reactions · 2 comments
- Mar 5, 2026Add SaleorGiftcardPaymentMethodDetails to transaction — saleor/saleor0 reactions · 2 comments
- Feb 25, 2026Fix failing smoke tests workflow — saleor/apps0 reactions · 3 comments
- Feb 13, 2026document payment method details in dashboard — saleor/saleor-docs0 reactions · 1 comment
- Feb 10, 2026Refund reasons phase 2 (POC) — saleor/saleor0 reactions · 1 comment
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- pinactSkill
- saleor-dashboard-cloud-extensionsSkill
- saleor-dashboard-detail-pagesSkill
- saleor-dashboard-entity-detailSkill
- saleor-dashboard-feedbackSkill
- saleor-dashboard-formsSkill
- saleor-dashboard-github-workflowsSkill
- saleor-dashboard-graphql-batchingSkill
- saleor-dashboard-listsSkill
- saleor-dashboard-loadingSkill
- saleor-dashboard-microcopySkill
- saleor-dashboard-security-auditSkill
- saleor-dashboard-smooth-shadowSkill
- saleor-dashboard-stylesSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 4 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Read .github/CONTRIBUTING.md under Pull requests for scope policy and .github/PULL_REQUEST_TEMPLATE.md for title and description …
- Very specific: line 24
If there is no PR (or gh is unavailable), use what exists locally:
- Very specific: line 35
Read .changeset/*.md files added on the branch.
- Distinctive: line 49
When there is more than one significant change, decide how they relate:
- Distinctive: line 58
Put the scope finding first in your report, not in a footnote.
- Very specific: line 77
Write a ready-to-paste title and description that pass step 3.
- Very specific: line 81
Remove optional sections only as the template permits.
- Distinctive: line 101
When step 2 found more than one significant change, propose a split:
- Very specific: line 113
Write the plan to .context/pr-split-plan.md when that directory exists.
- Distinctive: line 119
Keep it short, most important first:
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
PR quality check
Read .github/CONTRIBUTING.md under Pull requests for scope policy and
.github/PULL_REQUEST_TEMPLATE.md for title and description requirements. These
files are the sources of truth for the checks below.
This skill only reads and proposes. Every outward action (editing the PR, running the app for screenshots, creating branches) needs the user's explicit confirmation. Never push.
1. Gather the change
Find an open PR for the current branch:
gh pr view --json number,url,title,body,baseRefName,files,commits 2>/dev/nullIf there is no PR (or gh is unavailable), use what exists locally:
git log --format='%h %s' origin/main..HEAD
git diff --stat origin/main...HEAD
git status --shortInclude uncommitted changes. During planning, when nothing is written yet, check the plan itself: its goal and the list of changes it intends to make.
Read .changeset/*.md files added on the branch; they state the intended
user-visible change.
2. Check scope
Classify every change into one kind: bug fix, refactor, feature / behavior change, dependencies, tooling / CI, tests only, docs, generated (GraphQL types, lockfile, messages — these follow their source and do not count on their own).
Count significant changes. A change is significant when a reviewer would have to evaluate it on its own merits. Supporting edits that exist only to make the main change work do not count.
When there is more than one significant change, decide how they relate:
- Unrelated changes, or a change hidden inside another (for example a functional change in a refactor commit) → blocker. They must be split. Go to step 6.
- Connected changes (for example a refactor that enables the fix) → strongly recommend splitting and go to step 6. Say it is acceptable to keep them together only if each commit holds just its own change.
Put the scope finding first in your report, not in a footnote.
3. Check title and description
Against the PR template requirements, report each as pass / missing / weak:
- Title says what changes; user-facing wording for product changes, conventional prefix for internal ones.
- Problem, change (covering every area in the diff), non-obvious decisions, screenshots for UI, testing, links.
- The description mentions everything the diff touches. Flag any changed area the description does not mention — that is the most common gap.
- The PR template checkboxes are addressed.
Locally (no PR), check the commit messages and changesets the same way; they will become the PR text.
4. Propose title and description
Write a ready-to-paste title and description that pass step 3. Base it on the
diff, not on the existing text. Follow the headings and instructions in
.github/PULL_REQUEST_TEMPLATE.md; do not prescribe a separate format.
Remove optional sections only as the template permits. Keep its checkboxes at
the end. Leave a clear TODO for anything you could not determine instead of
inventing it.
5. Offer screenshots and a PR update
Screenshots — when the diff touches UI (src/**/*.tsx, *.module.css,
messages), propose taking before and after screenshots of the affected screens.
Name the screens and the state to capture. Ask for confirmation before
starting the app; it needs a backend and memory. Take "before" on origin/main
and "after" on the branch, save them under .context/, and show them to the user.
Update the PR — when a PR exists, offer to apply the proposed title and
description with gh pr edit <number> --title ... --body-file <file>. Show the
exact text first and ask for confirmation. Do not update without it. When no
PR is open, offer the text for gh pr create instead, and do not create it
unless asked.
6. Split plan and agent hand-off
When step 2 found more than one significant change, propose a split:
- One entry per future PR: title, kind, the files or hunks it takes, and which commits map to it.
- Order: prerequisites (refactors, dependency bumps) first; state which PR stacks on which, and whether each can merge independently.
- For each PR, a self-contained hand-off prompt another agent can run in its
own workspace: base branch, what to take from this branch
(
git checkout <branch> -- <paths>or specific commits), what to leave out, required checks fromAGENTS.md→ Verification, changeset yes/no, and the proposed PR title and description.
Write the plan to .context/pr-split-plan.md when that directory exists;
otherwise return it in the conversation. Ask for confirmation before
creating any branch or starting agents.
Report format
Keep it short, most important first:
- Scope: single change ✅, ⚠️ split recommended (connected), or ⛔ split required (unrelated or hidden) — list the changes found.
- Title / description: failing items only.
- Proposed title and description.
- Questions: screenshots? update the PR? create the split plan?
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

