npx skills add vouchdev/vouch --skill vouch-propose-from-pr --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# /vouch-propose-from-pr A PR is a decision: someone proposed a change, the team accepted it. The "why" gets compressed into the merge message and forgotten. This command preserves the why as cited claims in the KB. Steps: 1. Parse `$ARGUMENTS` as a PR URL or `<owner>/<repo>#<num>`; default to the most-recently-merged PR you authored. 2. Fetch the PR title, body, and the merged-commit SHA via `gh`. 3. Register the merge commit as a `kb_register_source` so subsequent claims can cite it. 4. Read the diff. For each *behavioural* change (not formatting / renaming), draft one `kb_propose_claim` whose text summarises the new invariant the code now upholds, citing the source from step 3. 5. Propose at most five claims per PR. If a PR is that big, suggest the contributor split it next time. Do not auto-approve. The KB's review gate is intentional; this command only fills the queue.
What does the vouch-propose-from-pr skill do?
Distill a merged PR into vouch claim proposals
How do I install it?
Run `npx skills add vouchdev/vouch --skill vouch-propose-from-pr --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.