Triage Failing Tests

Reproduce, diagnose, and fix failing Shiplight YAML tests. When tests break — due to UI changes, stale locators, changed flows, or assertion drift — triage systematically identifies what went wrong and fixes the tests. When the application itself is broken, triage reports the bug without modifying tests.

When to use

Use /shiplight:triage when:

• A test run comes back red and you need to fix the test suite
• After a deployment changed the UI and tests haven't caught up
• In CI pipelines to auto-fix flaky or broken tests before they block merges
• After a batch of UI changes that likely broke multiple tests

When NOT to use

Skip /shiplight:triage when:

• You need to create new tests from scratch — use /shiplight:create_e2e_tests
• You want to verify code changes look correct — use /shiplight:verify
• Tests pass but you want to improve test quality — manual review is better
• The application is intentionally being redesigned — rewrite tests instead