Grey.ooo/agent-standards
Watch
2
0
Fork
You've already forked agent-standards
 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions

Require durable image/video evidence on visual PRs, with a checklist #17

Merged
geusebio merged 3 commits from docs/durable-visual-evidence-requirement into main 2026-08-12 00:11:05 +00:00
Conversation 0 Commits 3 Files changed 2 +52 -15
geusebio commented 2026-08-12 00:00:31 +00:00
Owner
Copy link

Screenshots were already a hard requirement on PR bodies (VCS.md § Pull
requests), but two things were missing:

  • Video wasn't called out as equally required for interaction-heavy changes
    (a multi-step flow, drag-and-drop, an animation) — only screenshots were a
    named hard constraint.
  • "Durable" was implied (commit it, use a raw-branch link) but never made
    explicit as the actual requirement, and the existing raw-branch link
    pattern breaks once the branch is deleted post-merge — switched the
    preferred option to a commit-pinned link.

Adds an explicit pre-done checklist to VCS.md and cross-links it from
CLAUDE.md's "Show, don't just tell" section so both the rule and the
verification steps live in one place.

Docs-only change.

Screenshots were already a hard requirement on PR bodies (VCS.md § Pull requests), but two things were missing: - Video wasn't called out as equally required for interaction-heavy changes (a multi-step flow, drag-and-drop, an animation) — only screenshots were a named hard constraint. - "Durable" was implied (commit it, use a raw-branch link) but never made explicit as the actual requirement, and the existing raw-branch link pattern breaks once the branch is deleted post-merge — switched the preferred option to a commit-pinned link. Adds an explicit pre-done checklist to VCS.md and cross-links it from CLAUDE.md's "Show, don't just tell" section so both the rule and the verification steps live in one place. Docs-only change.
Screenshots were already a hard requirement on PR bodies, but nothing called
out video for interaction-heavy changes as equally required, or spelled out
what "durable" means (commit-pinned repo link or Forgejo attachment, not a
branch-pinned link or a chat-only screenshot). Adds an explicit checklist to
run through before calling a visual task done.
Small/low-risk PRs sat without a way to fast-track them beyond "wait for a
human to click merge" — but auto-enabling automerge unasked would be worse:
it removes the author's say on what "small" means for their repo. Ask via
an explicit choice control instead, scoped to genuinely low-risk changes.
geusebio scheduled this pull request to auto merge when all checks succeed 2026-08-12 00:10:37 +00:00 
A bare PR number forces the author to go look it up before they can
answer; the title is what actually lets them judge the offer.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Grey.ooo/agent-standards!17
No description provided.