gds-test-review

Analyze test suites to identify quality issues and coverage gaps.

Updated Nov 6, 2025
One-click install
npx skills add https://github.com/skyoxu/godotgame --skill gds-test-review-skyoxu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-test-review
Source: https://github.com/skyoxu/godotgame/tree/main/.agents/skills/gds-test-review
Command: npx skills add https://github.com/skyoxu/godotgame --skill gds-test-review-skyoxu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review test quality and coverage to prevent regressions and drift by providing structured analysis and actionable recommendations.

Core Features & Use Cases

  • Analyze the existing test suite to quantify coverage, identify gaps, and surface flaky or under-tested areas.
  • Produce a prioritized action plan and a shareable test-review report for stakeholders.
  • Use cases include pre-release quality checks, CI gate assessments, and post-release retrospectives to maintain test health.

Quick Start

Run the test review workflow against your project to generate a comprehensive report.

Frequently Asked Questions about gds-test-review

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

FAQPage Schema
How do I review test suite coverage and identify quality gaps?

To review test suite coverage, analyze unit, integration, and end-to-end tests across CI pipelines to quantify metrics, surface flaky areas, and generate a structured report with actionable recommendations.

What is risk-based prioritization for test reviews?

Risk-based prioritization for test reviews assesses test readiness by evaluating measurable metrics against potential regression risks, producing a prioritized action plan to address the most critical coverage gaps first.

Can I assess test readiness for both local development and CI pipelines?

Yes, you can assess test readiness for both local development and CI pipelines by defining the analysis scope to include unit, integration, and end-to-end tests across these environments to identify drift and quality issues.

When do I need a structured test review report?

You need a structured test review report during pre-release quality checks, CI gate assessments, and post-release retrospectives to maintain test health, prevent regressions, and provide stakeholders with measurable metrics and actionable recommendations.

What is the best way to prevent test regressions and drift?

The best way to prevent test regressions and drift is to analyze the existing test suite to quantify coverage, identify under-tested areas, and generate a prioritized action plan based on measurable metrics and risk assessment.