gui-verify

스타8

포크0

업데이트2026년 6월 17일 05:44

Behavioral GUI test harness for Irreden Engine creations. Builds a creation, runs it headless with the P3 GUI-test shot table, parses per-assertion PASS/FAIL from the result log, and exits non-zero on failure. Use after any GUI interaction change (hover routing, click dispatch, picking) to catch behavioral regressions without a human in the loop.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

출처

jakildev

jakildev/IrredenEngine

GitHub 저장소 열기 Creator 저장소 보기

다운로드

GUI Verify

Thin wrapper over the shared flow at docs/agents/skills/gui-verify.md. Read that doc for the full step sequence, anti-patterns, and image-comparison integration notes.

Deltas (engine repo)

Delta key	Engine value
runner	`scripts/gui-verify.py`
build tool	`fleet-build`
run tool	`fleet-run`
warmup default	`10`

Quick reference

# Run GUI tests for the voxel editor (builds first):
python3 scripts/gui-verify.py IRVoxelEditor

# Skip the build step:
python3 scripts/gui-verify.py IRVoxelEditor --no-build

# Increase warmup frames if assertions are timing-sensitive:
python3 scripts/gui-verify.py IRVoxelEditor --warmup-frames 20

Worked example: voxel editor

creations/editors/voxel_editor/main.cpp ships two assertion shots (shots 4 and 5 in the kGuiTestShots[] table):

Shot index	Label	Assertions
4	`editor_gui_assert`	HOVERS(layer_list), CLICK_FIRES(layer_list), CHECKBOX(layer_visible, true), SLIDER_VALUE(fps_slider, fps, 0.5)
5	`editor_pick_voxel`	PICKS_VOXEL(ivec3(-1,-1,-1))

Run:

python3 scripts/gui-verify.py IRVoxelEditor

Expected: all assertions PASS; non-zero exit and a failing-assertion list if any state is wrong after synthetic input injection.

Adding GUI tests to a new creation

See docs/agents/skills/gui-verify.md § "Adding a first GUI test to a creation".

이 저장소의 다른 Skills

같은 저장소

review-pr

jakildev/IrredenEngine

Review an open GitHub PR on the Irreden Engine repo and post a structured review. Use when the user says "review PR <N>", "review #<N>", "review the last PR", "check my PR", "review any new PRs", "review the PR queue", "check for new PRs to review", "review the open PRs", or otherwise asks for a code review — and also invoke automatically from a persistent reviewer-loop session when `gh pr list` surfaces a PR that has not yet been reviewed by this fleet. Designed to be invoked by a dedicated reviewer agent (dispatched into a pool worktree) whose job is to look at another agent's work with a fresh context. Writes a structured review covering ownership, ECS invariants, allocation hot paths, naming, tests, and project-specific smells, then posts it as a PR comment.

2026-07-268

simplify

jakildev/IrredenEngine

Polish the dirty working tree before committing — catch Irreden-Engine smells that a reviewer would otherwise flag. Use whenever you're about to commit, after addressing review feedback, after amending a commit, or whenever the user says "simplify", "clean up", "polish", "self-review", or "review my changes". Also auto-invoked by commit-and-push before the commit message is drafted. The skill finds per-entity getComponent in tick functions, allocation in hot loops, ECS naming convention slips, opportunities to reuse existing helpers, dead code, debug logs left behind, tautological comments, triple-nested loops over voxel volumes, renderer leaks from creation code, CPU-side SDF grid evaluation, linear-search in save/load hot paths, and stale or drifting CLAUDE.md / role / skill docs. Dispatches a parallel reuse-detection subagent fan-out so the reuse pass runs concurrently with the main checks. Applies safe fixes inline and reports anything that needs human judgment. Saves a review-fix-rereview round-trip.

2026-07-268

commit-and-push

jakildev/IrredenEngine

Stage, commit, push a feature branch, and open a GitHub PR against master for the Irreden Engine repo. Use whenever the user says "commit", "commit my changes", "commit and push", "open a PR", "make a PR", "wrap up this chunk", or otherwise indicates the current slice of work is ready for review. The skill assumes the parallel-agent workflow where work happens on short-lived feature branches, another agent reviews the PR, and the user merges via the GitHub UI. NEVER commit directly to master.

2026-07-218

platform-catchup

jakildev/IrredenEngine

Process the backlog of `fleet:needs-<host>-smoke` PRs on the current host. Builds a representative demo cohort against current `origin/master`, runs each with `--auto-screenshot`, and on green batch-swaps `fleet:needs-<host>-smoke` → `fleet:verified-<host>` on every eligible merged PR. On red (build break), files / opens a fix PR for the offender and holds labels on PRs that touch the implicated source paths until the fix lands. On partial (per-demo runtime hang or crash but build green), sweeps the rest, then fix-forwards the offending demo this session (issue only as the documented fallback). Runs on Linux, macOS, AND native Windows (MSYS2 mingw64) — Windows is now the primary validation host. Use when the human cues "platform-catchup", "catch up smoke tests", or "catch up Windows builds". Skill is **cue-only**, never auto-run — multi-target builds and ~40-demo runs are expensive, the human chooses when to spend them.

2026-07-158

render-debug-loop

jakildev/IrredenEngine

Build, run, and visually evaluate a rendering demo in an automated loop. Captures screenshots across a demo's configured shot list (zoom, camera offset, render-mode combinations), reads each image, diagnoses rendering issues against a topic-indexed reference (trixel / SDF shapes, lighting, backend parity), applies fixes, and repeats. Use whenever iterating on render pipeline bugs, shape alignment, lighting, parity drift, or any visual regression in the engine.

2026-07-158

render-verify

jakildev/IrredenEngine

Automated pass/fail render-regression harness for Irreden Engine demos. Wraps build → run → capture → compare → report: builds a demo, runs it with `--auto-screenshot`, then compares each shot against a committed reference image using a stdlib-only Python comparator. Reports per-shot pass/fail with diff images written for mismatches. Use after any render pipeline change to catch visual regressions automatically, or as a sanity pass on `master` before cutting releases.

2026-07-158

name	gui-verify
description	Behavioral GUI test harness for Irreden Engine creations. Builds a creation, runs it headless with the P3 GUI-test shot table, parses per-assertion PASS/FAIL from the result log, and exits non-zero on failure. Use after any GUI interaction change (hover routing, click dispatch, picking) to catch behavioral regressions without a human in the loop.

GUI Verify

Thin wrapper over the shared flow at docs/agents/skills/gui-verify.md. Read that doc for the full step sequence, anti-patterns, and image-comparison integration notes.

Deltas (engine repo)

Delta key	Engine value
runner	`scripts/gui-verify.py`
build tool	`fleet-build`
run tool	`fleet-run`
warmup default	`10`

Quick reference

# Run GUI tests for the voxel editor (builds first):
python3 scripts/gui-verify.py IRVoxelEditor

# Skip the build step:
python3 scripts/gui-verify.py IRVoxelEditor --no-build

# Increase warmup frames if assertions are timing-sensitive:
python3 scripts/gui-verify.py IRVoxelEditor --warmup-frames 20

Worked example: voxel editor

creations/editors/voxel_editor/main.cpp ships two assertion shots (shots 4 and 5 in the kGuiTestShots[] table):

Shot index	Label	Assertions
4	`editor_gui_assert`	HOVERS(layer_list), CLICK_FIRES(layer_list), CHECKBOX(layer_visible, true), SLIDER_VALUE(fps_slider, fps, 0.5)
5	`editor_pick_voxel`	PICKS_VOXEL(ivec3(-1,-1,-1))

Run:

python3 scripts/gui-verify.py IRVoxelEditor

Expected: all assertions PASS; non-zero exit and a failing-assertion list if any state is wrong after synthetic input injection.

Adding GUI tests to a new creation

See docs/agents/skills/gui-verify.md § "Adding a first GUI test to a creation".