attach-screenshots

Automating visual diffs for PR review involves running paired demo sequences against origin/master and the dirty working tree to capture before/after screenshots. This process produces labeled PNGs and a PR-ready Markdown snippet for reviewers to see rendering changes.

Yes, before/after screenshots for shader or demo code changes can be generated without local execution by running an auto-screenshot-capable demo against both origin/master and the dirty tree. The skill handles building, running, and validating shot counts automatically.

Capturing PR screenshots requires running paired demo sequences on baseline and current code, saving labeled PNGs under docs/pr-screenshots/<branch>/. The process generates a Markdown snippet with raw GitHub URLs that teams can paste directly into the PR discussion body.

A configured build environment and a writable repo are required to automate screenshot captures for engine rendering PRs. The process performs two builds and runs, handles stashing changes, and restores the working state as needed, requiring proper build setup.

Screenshot automation handles uncommitted changes by automatically stashing them before running the baseline build and demo sequence. After capturing the paired outputs, it restores the original working state, ensuring no data loss during the visual diff generation process.

Automated screenshot generation should be triggered when a PR touches rendering-related code, shaders, or demos. This ensures reviewers can visualize the visual delta and rendering changes without needing to build the engine or run the executable themselves.