From bcf15354d236cc33d191653978e4a81c2a91cc96 Mon Sep 17 00:00:00 2001 From: Jeroen Schweitzer Date: Mon, 6 Apr 2026 23:32:06 +0200 Subject: [PATCH] chore(skills): improve pr-review fresh-start instructions MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Clarify that every /pr-review invocation must start fresh — fetch, check PRs, and re-read the diff even if the branch was reviewed earlier in the same conversation. Co-Authored-By: Claude Opus 4.6 --- .claude/skills/pr-review/SKILL.md | 19 ++++++++++++------- 1 file changed, 12 insertions(+), 7 deletions(-) diff --git a/.claude/skills/pr-review/SKILL.md b/.claude/skills/pr-review/SKILL.md index f90de4422..f2689655b 100644 --- a/.claude/skills/pr-review/SKILL.md +++ b/.claude/skills/pr-review/SKILL.md @@ -62,18 +62,23 @@ Pre-existing warnings are not PR blockers but should be tracked for cleanup. ### 1. Determine the branch to review -If the user provided a branch name as argument, use it. Otherwise list open -PRs and ask the user which branch to review. +**Always start fresh.** Even if you reviewed this branch before in this +conversation, the branch may have new commits, a new PR, or main may have +moved. Do NOT skip steps or reuse earlier results. Every `/pr-review` +invocation is a full review cycle. + +**Always fetch and check for PRs first:** -To list open PRs on Gitea: ```bash +git fetch --all tea pr list --login schweitz --repo jpmschweitzer/settled-reach --state open --output simple ``` -Fetch remote branches first: -```bash -git fetch --all -``` +Then determine the branch: +- If the user provided a branch name as argument, match it to an open PR. + If a PR exists for that branch, note the PR number. If no PR exists, + proceed with the branch diff but note "no PR found" in the output. +- If no argument was given, list open PRs and ask which to review. ### 2. Determine reviewer team