capture-screenshots

Run the capture flow against your feature branch: it detects affected platforms from changed files, checks out the base branch in a detached git worktree, runs the platform screenshot tooling in both trees, and generates a markdown Visual Changes comparison table.

Paparazzi handles JVM-only screenshot testing for Jetpack Compose without an emulator, swift-snapshot-testing captures SwiftUI previews via xcodebuild, and Playwright takes headless browser screenshots of React or Next.js pages including dark mode and mobile viewports.

Yes, pass --base <branch> to diff against any base such as an epic integration branch. Without the flag, the base defaults to the remote HEAD branch, and all captures run against origin/<base> rather than a local ref.

git stash pop on a clean tree can pop someone else's stash since the stash stack is shared across worktrees, and checkout of the default branch fails when it is already checked out elsewhere. A detached worktree avoids both problems and never mutates the current tree.

The skill detects missing tooling by grepping build files and package.json, then emits the SCREENSHOTS_TOOLING_MISSING token and prints manual capture instructions. It never reports success for platforms where no screenshots exist on disk.