OpenParable
Skip to content
← Back to skills

Unity Testability

Testing & Quality
unity-testability

Unity Testability is an Agent Skill for testing & quality published in the Besty0728/Unity-Skills repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Advises on Unity testability — isolating logic out of MonoBehaviour and planning EditMode/PlayMode tests. Use when improving testability, extracting logic for unit tests, or planning a test strategy, even if the user just says "怎么测试" or "代码不好测". 为 Unity 可测试性提供建议(把逻辑从 MonoBehaviour 中剥离、规划 EditMode/PlayMode 测试);当用户要提升可测试性、为单元测试抽取逻辑、或规划测试策略时使用。

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/Besty0728/Unity-Skills/blob/HEAD/SkillsForUnity/unity-skills~/skills/testability/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/unity-testability, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Unity Testability Advisor

Use this skill when deciding what logic should remain in Unity-facing classes and what should move into pure C# code.

Review Questions

  • Can the rule/algorithm run without Transform, GameObject, or scene state?
  • Can config be injected instead of read through static globals?
  • Can runtime decisions be moved to a plain C# class and called from a thin MonoBehaviour?
  • Does this need PlayMode coverage, or is EditMode enough?

Output Format

  • Logic that should move to pure C#
  • Logic that should stay Unity-facing
  • Suggested seams/interfaces
  • Candidate EditMode tests
  • Candidate PlayMode tests

Guardrails

Mode: Documentation only — no REST skills to gate; load freely under any operating mode (Approval / Auto / Bypass).

  • Do not force test seams everywhere if the script is tiny and scene-bound.
  • Prefer a few meaningful seams over abstraction for its own sake.