From e9d6ea711515d12f0016ec879d580784fe6372b4 Mon Sep 17 00:00:00 2001 From: Vinta Chen Date: Sun, 16 Aug 2026 21:21:21 +0800 Subject: [PATCH] docs: reword review-prs stale-base rationale to be rate-free The "most diffs sit on stale bases" claim was a one-time artifact of the shortlist reform, not a durable fact about future PRs. Reworded to state that diff context lines show the base the PR was written on, which may have changed since, while keeping conflict-to-Merge-arm routing. Co-Authored-By: Claude --- .claude/skills/review-prs/SKILL.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.claude/skills/review-prs/SKILL.md b/.claude/skills/review-prs/SKILL.md index 6555ac69..e3d2cdda 100644 --- a/.claude/skills/review-prs/SKILL.md +++ b/.claude/skills/review-prs/SKILL.md @@ -18,7 +18,7 @@ Sort the batch: entry additions continue; anything else (typo fixes, website cha Apply the Automatic Rejection rules that the diff and PR metadata answer without judgment. The recently-closed-duplicate rule needs a lookup: `gh pr list --repo vinta/awesome-python --state closed --search "" --limit 10`. A screened-out PR goes straight to step 4 as a close, with the rule it broke as its reason. -Resolve each survivor's target use case against the current README, since most diffs sit on stale bases and their context lines show sections that no longer exist. A merge conflict is a symptom of that stale base — it rides to the Merge arm, which absorbs it. Done when every surviving PR names its target use case. +Resolve each survivor's target use case against the current README — a diff's context lines show the base the PR was written on, which may have changed since. A merge conflict rides to the Merge arm, which absorbs it. Done when every surviving PR names its target use case. ## 3. Judge