Dev enforces screenshot proof on every frontend PR via an agent skill
SeanOliver · x · 2026-09-26
A developer shares the hard rules baked into his PR-finalizing agent skill: every frontend PR must attach screenshots for each changed UI element.
- The shot list is generated from the diff: one row per element and per affected state (empty, error, hover, dark mode)
- Existing UI gets before/after pairs; new UI only needs after shots
- The agent must actually open each image before attaching — a login wall or loading spinner doesn't count
- Skipping requires a written reason per UI file
Before trusting it on real PRs, he had a fresh agent review the skill against three made-up PRs; it surfaced 11 unclear instructions, 8 of which he fixed.
More from coding & agent
- Reasonable Team Publishes TLA+ Tutorial: Not a Silver Bullet, AI Agents Could Change That — fhuszar · 2026-09-26
- Using Opus 5.5 to make a video explaining Algorithm W and Hindley-Milner type inference — ctjlewis · 2026-09-26
- Runway MCP brings Gen-4.5 video and image generation into Claude chats — runwayml · 2026-09-26
- One 'Harmless' Agent Permission Turned Into a Backdoor for Everyone — Adorable-Algae6903 · 2026-09-26
- DEV·TV: a single-HTML-file TV playing Hugging Face models and AI papers hits Product Hunt — TradingCardGirl · 2026-09-26
- MCP Wallet Agents Need Boring Permission Rules Before Going Agentic — Any-Sir-7622 · 2026-09-26