Agent skill · AI & Agents

pr-precheck

Use when the user invokes `/pr-precheck <repo> <topic>` or — implicitly, before any other skill opens a pull request — to check the target repo's merged and closed PR history for prior attempts at the same fix, so the agent doesn't open the Nth duplicate of an already-rejected approach. Wraps the `vouch pr-cache` CLI (build / check / show) and turns its verdict into a clear stop / ask / proceed signal.

vouchdev120★ · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add vouchdev/vouch --skill pr-precheck --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 8 KB
Bundled scripts: none
Path: skills/pr-precheck/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 120
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# PR Precheck **Goal:** before you raise a PR, find out whether someone already tried this fix — especially whether anyone tried and got *rejected*. The cost of asking is seconds; the cost of a duplicate PR is reviewer attention, contributor reputation, and (on Bittensor-style mining repos) wasted scoring weight. This skill is a thin orchestration layer over the `vouch pr-cache` CLI shipped in vouch ≥ this PR. It's safe to invoke directly **and** to chain ahead of `pr-fix` / `prs-auto`. ## Invocation Direct: ``` /pr-precheck <repo> <topic-summary> /pr-precheck <repo> <topic-summary> --files a.py,b.py ``` Implicit (auto-fires inside `pr-fix` / `prs-auto` before the "open PR" step): ``` /pr-fix https://github.com/owner/repo/issues/N └─ before pushing the branch, run pr-precheck on the planned PR title + files ``` `<repo>` may be: - `https://github.com/<owner>/<name>` - `git@github.com:<owner>/<name>.git` - `<owner>/<name>` (shorthand) `<topic-summary>` is the title-like phrase that describes the PR you're about to raise. Be specific — short generic strings ("fix bug") will match too many cached PRs. ## Prerequisites - **`vouch` CLI** on `PATH` (`pip install vouch-kb` ≥ the version th

What's inside
Steps it walks through
  1. Invocation
  2. Prerequisites
  3. Step 1 — Ensure cache is present and fresh
  4. Step 2 — Run the check
  5. Step 3 — Branch on the verdict
  6. Step 4 — Report to the user
  7. Failure modes
  8. Why this exists
  9. Integration hook for pr-fix / prs-auto
Commands it runs
if [ ! -f "$CACHE" ] || [ "$(find "$CACHE" -mmin +1440 -print 2>/dev/null)" ]; then
vouch pr-cache build "$REPO_URL" --state all --limit 200
fi
vouch pr-cache build "$REPO_URL" --analyze-closed
vouch pr-cache check "$REPO" \
case "$(echo "$PRECHECK" | jq -r .verdict)" in
esac
More from vouch
All skills →
About this skill
What does the pr-precheck skill do?

Use when the user invokes `/pr-precheck <repo> <topic>` or — implicitly, before any other skill opens a pull request — to check the target repo's merged and closed PR history for prior attempts at the same fix, so the agent doesn't open the Nth duplicate of an already-rejected approach. Wraps the `vouch pr-cache` CLI (build / check / show) and turns its verdict into a clear stop / ask / proceed signal.

How do I install it?

Run `npx skills add vouchdev/vouch --skill pr-precheck --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From vouchdev/vouch, a repository with 120 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going