proofshot

Other Community

Skill notes

When to use

Use ProofShot after: Building a new UI feature or page Modifying existing UI components Fixing a visual bug Any change that affects what the user sees

Step 1: Start the session

This opens a browser and begins recording. If the port is already in use, proofshot will kill the existing process automatically. Always use --run to let proofshot start and capture your dev server output (server logs appear in the proof report). Only omit --run if the server was explicitly started by the user or another process — without it, no server logs are captured. If a previous session was not stopped cleanly, add --force to override it.

Step 2: Drive the browser and test

Use proofshot exec to navigate, interact, and verify: Take screenshots at important moments — these become the visual proof. Verify what you expect to see by reading the snapshot output.

Step 3: Stop and bundle the proof

This stops recording, collects console + server errors, and generates a SUMMARY.md with video, screenshots, and error report.

Step 4 (optional): Post proof to the PR

This uploads screenshots and video to GitHub and posts a formatted comment on the PR. By default it uses the official GitHub contents API on a proofshot-artifacts branch. Use --upload-provider github-web-attachments if you specifically want GitHub attachment URLs.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@AmElmo · MIT
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Start the session

This opens a browser and begins recording. If the port is already in use, proofshot will kill the existing process automatically. Always use `--run` to let proofshot start and capture your dev server output (server logs appear in the proof report). Only omit `--run` if the server was explicitly started by the user or another process — without it, no server logs are captured. If a previous session was not stopped cleanly, add `--force` to override it.

02
Step 2: Drive the browser and test

Use proofshot exec to navigate, interact, and verify: Take screenshots at important moments — these become the visual proof. Verify what you expect to see by reading the snapshot output.

03
Step 3: Stop and bundle the proof

This stops recording, collects console + server errors, and generates a SUMMARY.md with video, screenshots, and error report.

04
Step 4 (optional): Post proof to the PR

This uploads screenshots and video to GitHub and posts a formatted comment on the PR. By default it uses the official GitHub contents API on a `proofshot-artifacts` branch. Use `--upload-provider github-web-attachments` if you specifically want GitHub attachment URLs.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.