test-strategy-review

Plan risk-aware test strategies for Godot/.NET changes with a prioritized test matrix.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/LoogacyStudio/skills --skill test-strategy-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-strategy-review
Source: https://github.com/LoogacyStudio/skills/tree/main/plugins/godot-dotnet/skills/test-strategy-review
Command: npx skills add https://github.com/LoogacyStudio/skills --skill test-strategy-review

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Identify and plan an efficient, risk-aware test strategy for Godot/.NET changes by separating pure logic from runtime-dependent behavior and producing a minimal, prioritized test matrix.

Core Features & Use Cases

  • Generate structured test strategies covering six layers: pure logic, runtime-dependent, scene/integration, UI/flow, smoke, and regression.
  • Produce a minimal test matrix (assets/test-matrix.md) with concrete targets and regression priorities.
  • Provide guidance for separating logic vs. runtime orchestration, improving test quality while reducing cost.
  • Support decision-making for feature additions, bug fixes, migrations, and UI changes in Godot/.NET projects.

Quick Start

Describe the change surface and activation, then run the skill to produce a complete test strategy and matrix.

Frequently Asked Questions about test-strategy-review

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

FAQPage Schema
How do I plan a test strategy for Godot/.NET changes that separates pure logic from runtime behavior?

To plan a test strategy for Godot/.NET changes, you separate pure C# logic from runtime-dependent behavior to produce a minimal, prioritized test matrix. This approach reduces test cost while ensuring critical paths are covered.

What is a risk-aware test matrix and when do I need it for C# game development?

A risk-aware test matrix is a prioritized testing plan that targets specific layers like pure logic, runtime, UI, and smoke paths. You need it for Godot/.NET feature additions, bug fixes, migrations, and UI changes to minimize redundant tests.

Does this test planning approach work for both Godot UI changes and .NET backend migrations?

Yes, this test strategy approach works for Godot UI changes and .NET migrations by evaluating the change type and affected components. It generates tailored layer recommendations and regression plans for each specific scenario.

What's the best way to minimize regression risks when updating Godot/.NET projects?

The best way to minimize regression risks is to generate a targeted regression plan that identifies critical runtime and integration layers. This ensures you test necessary smoke paths without running expensive, redundant UI tests.

What inputs do I need to generate a test matrix for a Godot/.NET bug fix?

To generate a test matrix for a Godot/.NET bug fix, you need clear inputs about the change type, affected components, and upgrade considerations. The output includes a change summary, risk assessment, and explicit assumptions.