Proof of work on a pull request

Goal

Give the owner a phone-sized page of evidence for a pull request.

What you’ll have

Prompt

Proof of work on a pull request

Your agent builds the page and checks the result with you.

Copy promptCopiedUsing Super Artifacts, make a phone-sized proof for this pull request. Ask for its number and changed behavior. Read the pr-proof template with super_templates; fill its proof slot using real screenshots or diagrams, with brief captions and only verified outcomes. Publish with super_publish as pr-proof-<number>, explicitly private, then set it private again with super_artifact_set. Use super_project to create or find my proof project and set rule.match.slugStartsWith to pr-proof-. Keep its audience restricted unless I choose otherwise; ask before widening access. Return the proof and project links. If the pictures show unrelated work, replace them; if the project omits the proof, check the slug and rule.

Needs

• The pull request and evidence from its changed paths.
• A connected agent and the pr-proof template.

Steps

1. 01

   Evidence first

   The agent collects pictures of the changed behavior and checks the proof document.

2. 02

   One private page

   The pr-proof template turns that evidence into a phone-sized page.

3. 03

   One project rule

   A project rule matches slugs starting with pr-proof-; its audience decides who opens the project.

4. 04

   One review link

   The agent returns the page link for the pull request.

Check it worked

The owner opens the link on a phone; the correct pull request number and pictures appear. The project lists the proof.

If not

• Wrong change shown: The prompt asks the agent to replace unrelated evidence.
• Missing from the project: The prompt asks it to check the prefix rule and the artifact slug.

Variations

• A second publish updates the same proof after a fix.
• A separate project can collect proofs for another repository.

Next

• More on comments
• More on projects