/v3-test-heal

Diagnose and repair E2E test failures in OpenShift and KubeVirt environments.

Updated May 9, 2026

Search Tags:#automation #testing #debugging #self-healing #openshift #kubevirt

Ready to run

npx skills add https://github.com/Ruclo/thesis-artifact --skill v3-test-heal

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: /v3-test-heal
Source: https://github.com/Ruclo/thesis-artifact/tree/main/v3/skills/v3-test-heal
Command: npx skills add https://github.com/Ruclo/thesis-artifact --skill v3-test-heal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the high maintenance burden of E2E tests by automatically diagnosing failures, applying fixes based on repository patterns, and documenting lessons learned to prevent future regressions.

Core Features & Use Cases

Automated Self-Healing: Executes tests against a live cluster, parses tracebacks, and applies code fixes in-place.
Knowledge Retention: Automatically updates a central GRAVEYARD.md file with documented mistakes and actionable avoidance strategies.
Use Case: When a test fails due to a changed API signature or a missing fixture, the skill identifies the root cause, searches the codebase for the correct implementation, applies the fix, and verifies the resolution.

Quick Start

Run the v3-test-heal skill on the specified test file to automatically diagnose and fix any failures encountered during execution.

Frequently Asked Questions about /v3-test-heal

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

FAQPage Schema

How do I automatically fix failing end-to-end tests in OpenShift and KubeVirt?▼

Automated self-healing for E2E tests executes your suite against a live cluster, parses tracebacks from failures, and applies code patches in-place based on repository patterns to resolve issues.

What is the best way to prevent regressions when maintaining E2E test suites?▼

Preventing regressions involves retaining knowledge of past failures by automatically documenting mistakes and avoidance strategies in a centralized GRAVEYARD.md file for future reference.

How does automated test healing identify and resolve changed API signatures or missing fixtures?▼

Automated test healing identifies root causes by parsing execution logs, cross-referencing repository source code and documentation to find correct implementations, applying fixes, and verifying the resolution.

Can I run automated diagnostic and repair cycles for tests against a live OpenShift cluster?▼

Yes, you can run automated diagnostic and repair cycles against a live OpenShift cluster by iteratively executing tests, analyzing failures, and applying code fixes in-place.

Does automated self-healing for E2E tests require manual intervention for recurring failures?▼

No, it reduces manual intervention by iteratively executing tests, analyzing failures, applying code patches, and persisting resolution strategies in a centralized memory file to prevent future regressions.

Why does my E2E test suite require high maintenance after cluster updates?▼

E2E test suites require high maintenance because failures occur from changed APIs or missing fixtures, requiring automated diagnostic cycles to parse tracebacks and apply fixes based on repository patterns.