Visual regression checks on PRs before merge

[maxfindel]

Summary

Run FlowChad on PR branches before merge. Compare screenshots against baseline. Flag layout breakage, missing elements, broken flows.

How it works

• Trigger: PR opened/updated on repos with FlowChad installed
• Could be GitHub Action or Pylot mission (webhook: pull_request.opened / pull_request.synchronize)
• Run affected flows against the PR branch (start dev server from branch)
• Compare screenshots against main branch baseline using /flow-diff
• Post results as PR comment: pass/fail per flow + diff screenshots
• Block merge if critical flows fail (optional, per-repo config)

Maps to

• Nader's SDLC list Flow definition YAML schema and starter templates #14: "Automated visual regression tests before every PR"
• Nader's SDLC list report skill — friction report generation #5: "Auto-fix on every PR" (combined with review-pr)

Open questions

• GitHub Action vs Pylot dispatch? (Action = faster feedback, Pylot = no CI minutes cost)
• Baseline storage: committed screenshots or generated fresh from main?
• Which flows to run? All, or only those touching changed files?

🤖 Generated with Claude Code