vouch-propose-from-pr

スター156

フォーク60

更新日2026年7月2日 06:56

Distill a merged PR into vouch claim proposals

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

vouchdev

vouchdev/vouch

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

/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:

Parse $ARGUMENTS as a PR URL or <owner>/<repo>#<num>; default to the most-recently-merged PR you authored.
Fetch the PR title, body, and the merged-commit SHA via gh.
Register the merge commit as a kb_register_source so subsequent claims can cite it.
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.
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.

このリポジトリの他の Skills

同じリポジトリ

vouch-ask

vouchdev/vouch

Answer a question from the vouch KB with citations, or say what's missing

2026-07-04156

vouch-followup

vouchdev/vouch

Propose a dated followup the vouch digest will surface until closed

2026-07-04156

vouch-record

vouchdev/vouch

Propose a typed record (contact, org, project) into the vouch KB

2026-07-04156

vouch-remember

vouchdev/vouch

File something the user wants remembered as a cited, review-gated proposal

2026-07-04156

vouch-standup

vouchdev/vouch

Narrate the vouch digest — pending reviews, decisions, stale claims, due followups

2026-07-04156

vouch-recall

vouchdev/vouch

Recall what the project's vouch KB knows about a topic

2026-07-02156

name	vouch-propose-from-pr
description	Distill a merged PR into vouch claim proposals

/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:

Parse $ARGUMENTS as a PR URL or <owner>/<repo>#<num>; default to the most-recently-merged PR you authored.
Fetch the PR title, body, and the merged-commit SHA via gh.
Register the merge commit as a kb_register_source so subsequent claims can cite it.
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.
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.