verifying-scenes

Verifies scene mutations using snapshot diffs, framed screenshots, and live runtime reads.

66|4|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/SummerEngine/summer --skill verifying-scenes-summerengine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verifying-scenes
Source: https://github.com/SummerEngine/summer/tree/main/library/skills/verifying-scenes
Command: npx skills add https://github.com/SummerEngine/summer --skill verifying-scenes-summerengine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents often claim scene changes worked without proof, compounding errors on unverified state. This Skill enforces an evidence-first discipline: snapshot before every mutation batch, diff and screenshot after, and read live runtime state during playtests before making any claim. ## Core Features & Use Cases - Before/after verification loop: Capture a world snapshot before mutating, then run a snapshot diff and screenshot after to confirm exactly what was added, removed, or changed. - Stable viewpoint screenshots: Save camera bookmarks and capture annotated screenshots with numbered labels mapped to node paths, so before/after comparisons line up from the same pose. - Live runtime inspection: Read the actual running scene tree and inspect live node properties during playtests without stopping the game and resetting the bug. - Use Case: After a script places 40 trees in a scene, run the snapshot diff to confirm exactly 40 owned nodes were added, take a bookmarked camera screenshot to check lighting and scale, and cite both as evidence before continuing. ## Quick Start Verify the scene changes you just made by taking a world snapshot diff and a bookmarked camera screenshot, then report what each one proves.

Frequently Asked Questions about verifying-scenes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify scene changes in Summer Engine?

Take a world snapshot before mutating, then run a snapshot diff and a screenshot after. Check that added, removed, and changed entries match your intent, and look at the screenshot before claiming the work succeeded.

How do I take before and after screenshots from the same viewpoint?

Save a camera bookmark once with summer_camera_bookmark, then capture every screenshot with framing set to bookmark and that bookmark name. The pose is project-persisted, so comparisons stay aligned across sessions.

How do I inspect a running game without stopping it?

Use the runtime tree read to see what actually spawned, then inspect individual live nodes by path for their real properties. Stopping the game resets the state and usually destroys the bug you are chasing.

Does scene verification work on older Summer Engine versions?

Engines older than 0.5.66 lack the snapshot, diff, and runtime read operations and return engine_lacks_op. Fall back to the scene tree read plus screenshots for partial verification on those builds.

Why does my snapshot diff return unknown_snapshot?

The engine retains only the last 8 snapshots per session, so an old baseline id expires. Take a fresh snapshot and redo the before/after pair around your next mutation.

Can I judge lighting from a preset-framing scene screenshot?

No. Preset framings substitute a flat synthetic environment and cannot show real lighting or mood. Use camera framing to render through the scene's own camera and WorldEnvironment, or capture the running game.