Test Fixing Skill

Diagnose and repair failing automated tests through root cause analysis.

1|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/chrysaliscat/designgraduation --skill test-fixing-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Test Fixing Skill
Source: https://github.com/chrysaliscat/designgraduation/tree/main/.agent/skills/test-fixing
Command: npx skills add https://github.com/chrysaliscat/designgraduation --skill test-fixing-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the common and time-consuming issue of failing automated tests by providing a systematic approach to diagnosis and repair.

Core Features & Use Cases

  • Systematic Diagnosis: Guides users to read errors, check artifacts, and isolate failures.
  • Root Cause Analysis: Helps identify common issues like race conditions, data problems, and selector changes.
  • Self-Healing Loop: Implements a structured process for patching, verifying, and performing regression testing.
  • Use Case: When a critical end-to-end test for user login starts failing intermittently, this Skill can be used to analyze the failure, identify a potential race condition due to UI animation, and suggest a fix by adding appropriate waits.

Quick Start

Use the Test Fixing Skill to diagnose and repair the failing 'user-creation' test.

Frequently Asked Questions about Test Fixing Skill

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

FAQPage Schema
How do I fix failing automated tests that have assertion and timeout errors?

The best way to debug failing automation tests is through a self-healing methodology that guides you through error reading, artifact checking, and root cause analysis, followed by patching, verifying, and regression testing.

How do I debug intermittent test failures caused by race conditions?

To debug intermittent race condition test failures, you analyze UI animations or timing issues and apply fixes by adding appropriate waits, systematically verifying the patch through regression testing.

What is a self-healing loop for test maintenance?

A self-healing loop for test maintenance is a structured process for systematically patching failing tests, verifying the fix, and performing regression testing to ensure stability.

Can I use this systematic diagnosis approach for Playwright end-to-end tests?

Yes, you can use this systematic diagnosis approach for Playwright end-to-end tests to address reference errors, timeouts, and assertion failures by isolating the root cause and applying verified patches.

Why does my automated test maintenance fail when UI selectors change?

Automated test maintenance fails when UI selectors change because the underlying references break, requiring a root cause analysis to identify the selector update and patch the test through a verification loop.