pr
Installation
SKILL.md
Turn committed work into a draft PR a reviewer trusts in under a minute: what changed, proof it works, and how risky it is to merge. The draft is the gate: the human marks it ready, so you open it and stop.
The skill starts once the code is committed and ends at a published draft. Scratch lives outside the repo: SCRATCH="${TMPDIR:-/tmp}/pr-<branch>". Screenshots and logs stay there, off the branch, and are kept after upload so revisions can reuse them.
Steps
- Shape. Decide how many PRs this work becomes and each one's base, per Shape. Done when every change belongs to exactly one PR and each PR has a base.
- Claims. Read the diff GitHub will show (
git diff origin/<base>...HEAD) and write each change as a claim: one sentence a reviewer could check by looking or running. Done when every changed file sits under a claim or is named in the Scope line. - Proof. Prove each claim with the lowest rung of the proof ladder that carries it. Done when every claim has its proof or a "Not verified: " line.
- Body. Write
$SCRATCH/body.mdand a title, per Body. Done when every claim appears in Evidence and every referenced file exists. - Publish. Push and open or update the draft, per Publish. Done when the read-back passes.
- Report. Post the PR URL, one line on what was proved and one on what wasn't, then stop. A helper under an orchestrator reports per delegate.
Shape
Ask of each change: would this build, pass CI and make sense if it were the only thing merged into main?