verify

Runs Unity EditMode tests to validate GameFlow, Card, and Economy code changes.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/DJackyB/Project_Rent --skill verify-djackyb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/DJackyB/Project_Rent/tree/main/.claude/skills/verify
Command: npx skills add https://github.com/DJackyB/Project_Rent --skill verify-djackyb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After modifying core gameplay code such as GameFlow, Card, or Economy systems, there is no automated CI/CD pipeline to catch regressions. This Skill guides you through manually running Unity EditMode tests in the Editor to confirm that recent changes have not broken core flows like the reward selection chain. ## Core Features & Use Cases - Guided Test Execution: Step-by-step instructions for opening the Unity Test Runner (Window → General → Test Runner), selecting the EditMode tab, and running all or selected tests. - Failure Triage Guidance: Directs you to inspect the Console window's error stack traces and fix root causes instead of bypassing failing tests. - Use Case: You just refactored the card reward logic in a Unity project. Use this Skill to run the EditMode test suite covering the reward selection flow and verify nothing regressed before committing. ## Quick Start Run the Unity EditMode tests to verify my recent changes to the GameFlow code did not break the reward selection flow.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I run EditMode tests in Unity Editor?▼

Open the Unity Editor, go to Window → General → Test Runner, select the EditMode tab, then click Run All to execute every test or select a specific test class and click Run Selected.

How to verify Unity game code changes without CI/CD?▼

Manually trigger EditMode tests through the Unity Test Runner window after each change to core systems. Since there is no automated pipeline, all tests must be run by hand in the Editor before considering changes complete.

What Unity test framework version is needed for EditMode tests?▼

This workflow uses com.unity.test-framework version 1.6.0. Tests are located in Assets/_Assets/Scripts/Tests/ or Assets/Tests/ directories and run in EditMode without entering Play mode.

Why do Unity EditMode tests fail after code changes?▼

Failures typically indicate regressions in modified systems like GameFlow, Card, or Economy logic. Check the Console window for error stack traces, identify the root cause, and fix the underlying code rather than bypassing the failing test.

What test coverage exists for Unity reward selection logic?▼

Current known test coverage includes the reward selection chain (reward link). Coverage is limited, so passing tests confirm the reward flow works but do not guarantee all gameplay systems are validated.