openmates:fix-tests

Triage failing test runs into root-cause groups and apply targeted fixes.

43|2|Updated Jan 25, 2024
One-click install
npx skills add https://github.com/glowingkitty/OpenMates --skill openmates-fix-tests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openmates:fix-tests
Source: https://github.com/glowingkitty/OpenMates/tree/main/.claude/skills/fix-tests
Command: npx skills add https://github.com/glowingkitty/OpenMates --skill openmates-fix-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly identify the root causes of the latest failing tests and apply focused fixes so the suite returns to green.

Core Features & Use Cases

  • Delegated failure triage: Uses the test-failure-triager subagent to produce grouped root-cause analysis and suggested fix locations.
  • Root-cause-first repairs: Applies fixes for the highest-tier groups first, grouped by root cause rather than individual tests.
  • Fail-safe console error handling: Ensures that console.error-origin root causes are fixed in application code rather than suppressed in tests.
  • Controlled reruns: Reruns only the failed specs via scripts/run_tests.py to verify each change.

Quick Start

Ask the assistant to run the openmates:fix-tests workflow to triage the latest failures from the most recent daily run and patch the grouped root causes, then rerun only the failed specs to confirm all are green.

Frequently Asked Questions about openmates:fix-tests

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

FAQPage Schema
How do I triage and fix failing automated tests by their root cause?

To triage and fix failing automated tests by root cause, this Skill groups latest daily run failures into root-cause categories, applies targeted code changes at suggested locations, and verifies fixes by rerunning failed specs.

What is the best way to analyze nightly test failure patterns across multiple specs?

Analyzing nightly test failure patterns across multiple specs requires persisted JSON failure reports and nightly pattern consistency logs. The Skill processes these inputs to identify and group recurring test failures by their underlying root cause.

How do I fix console.error test failures without suppressing the error in my tests?

Fixing console.error test failures without suppressing them requires applying root-cause-first repairs in the application code itself. The Skill ensures console.error-origin root causes are fixed in application logic rather than suppressed in test files.

Does this test regression fixing workflow work with Playwright and Vitest?

Yes, this test regression fixing workflow applies to test failure analysis across multiple specs using Playwright and Vitest. It reruns only the failed specs through scripts/run_tests.py to verify applied code changes return the suite to green.

What limitations exist when fixing failing tests grouped by root cause?

A key limitation when fixing failing tests grouped by root cause is that this workflow requires delegated triage via a test-failure-triager subagent. It relies on persisted JSON failure reports and depends on scripts/run_tests.py for controlled reruns.