verify-changes

Run play mode tests and fix common Unity errors automatically.

64|4|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/gamekit-agent/gamekit-cli --skill verify-changes-gamekit-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-changes
Source: https://github.com/gamekit-agent/gamekit-cli/tree/main/template/.claude/skills/verify-changes
Command: npx skills add https://github.com/gamekit-agent/gamekit-cli --skill verify-changes-gamekit-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill prevents the accumulation of broken code by automatically testing and fixing changes before proceeding to the next task, ensuring a stable codebase.

Core Features & Use Cases

  • Automated Testing: Runs quick play mode tests and checks console logs for errors after any code modification.
  • Error Fixing Loop: Attempts to automatically fix common errors like NullReferenceException or missing components.
  • Use Case: After adding a new enemy AI script, this Skill will automatically enter play mode, check for errors, and if any arise, attempt to fix them before allowing the development process to continue.

Quick Start

Run an automated test-fix loop on the latest code changes.

Frequently Asked Questions about verify-changes

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

FAQPage Schema
How do I automate code verification for Unity play mode tests after making changes?

Automated code verification in Unity executes a test-fix loop by running quick play mode tests and analyzing console logs for errors. It automatically attempts to fix common issues like NullReferenceExceptions up to three times before escalating.

Can I automatically fix NullReferenceException errors in Unity during CI/CD testing?

Yes, automated Unity testing can fix NullReferenceException errors during CI/CD workflows. The test-fix loop analyzes console logs and applies automatic fixes for missing components and null references up to three times before escalating to user guidance.

What is the best way to prevent broken code from accumulating in a Unity project?

Automated code verification prevents broken code accumulation by testing and fixing changes before moving to the next task. It enters Unity play mode, checks for console errors, and attempts automatic fixes to ensure a stable codebase.

How does the test-fix loop work when debugging Unity console errors?

The test-fix loop for Unity console errors iterates up to three times by running play mode tests, analyzing console logs, and applying automatic fixes for common issues. If unresolved after three attempts, it escalates to user guidance or a code debugger agent.

What happens if automated error fixing fails to resolve Unity play mode errors?

If automated error fixing fails to resolve Unity play mode errors after three iterations, the test-fix loop escalates the issue. It provides user guidance or routes the unresolved errors to a dedicated code debugger agent for manual intervention.