$npx -y skills add vouchdev/vouch --skill vouch-propose-from-prDistill a merged PR into vouch claim proposals
| 1 | # /vouch-propose-from-pr |
| 2 | |
| 3 | A PR is a decision: someone proposed a change, the team accepted it. The |
| 4 | "why" gets compressed into the merge message and forgotten. This command |
| 5 | preserves the why as cited claims in the KB. |
| 6 | |
| 7 | Steps: |
| 8 | |
| 9 | 1. Parse `$ARGUMENTS` as a PR URL or `<owner>/<repo>#<num>`; default to the |
| 10 | most-recently-merged PR you authored. |
| 11 | 2. Fetch the PR title, body, and the merged-commit SHA via `gh`. |
| 12 | 3. Register the merge commit as a `kb_register_source` so subsequent claims |
| 13 | can cite it. |
| 14 | 4. Read the diff. For each *behavioural* change (not formatting / renaming), |
| 15 | draft one `kb_propose_claim` whose text summarises the new invariant the |
| 16 | code now upholds, citing the source from step 3. |
| 17 | 5. Propose at most five claims per PR. If a PR is that big, suggest the |
| 18 | contributor split it next time. |
| 19 | |
| 20 | Do not auto-approve. The KB's review gate is intentional; this command |
| 21 | only fills the queue. |