refactor: deduplicate fix-e2e skills by removing redundant mapping tables

Skills now reference the e2e-fix-workflow rule for mapping tables
(job→branch, job→platform, branch→image repo/tag) instead of
duplicating them. This reduces token usage by ~40% while keeping
the unique procedural value each skill provides:

- parse-ci-failure: structured output template with derivation
  details, GCS URLs, and flag breakdown table
- deploy-rhdh: concrete example command, prominent CLI mode warning
- diagnose-and-fix: "Try Healer Agent First" callout, removed
  duplicated coding conventions (~80 lines)
- reproduce-failure: removed duplicated project reference table
- submit-and-review: prominent dynamic GITHUB_USER extraction,
  removed CI check types table

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: zdrapela

.claude/skills/deploy-rhdh/SKILL.md

@@ -51,30 +51,30 @@ Vault authentication, cluster service account setup, RHDH deployment, and test e
 
 ### CLI Mode (Preferred)
 
-CLI mode requires **all three** flags (`-j`, `-r`, `-t`) to avoid falling into interactive mode:
+**CRITICAL**: CLI mode requires **all three** flags (`-j`, `-r`, `-t`). If `-r` is omitted, the script falls into interactive mode and will hang in automated contexts.
 
 ```bash
 cd e2e-tests
 ./local-run.sh -j <full-prow-job-name> -r <image-repo> -t <image-tag> [-s]
 ```
 
+**Example** — deploying for a main branch OCP Helm nightly job (deploy-only):
+```bash
+cd e2e-tests
+./local-run.sh -j periodic-ci-redhat-developer-rhdh-main-e2e-ocp-v4-20-helm-nightly -r rhdh-community/rhdh -t next -s
+```
+
 **Parameters:**
 - `-j / --job`: The **full Prow CI job name** extracted from the Prow URL. The `openshift-ci-tests.sh` handler uses bash glob patterns (like `*ocp*helm*nightly*`) to match, so the full name works correctly. Example: `periodic-ci-redhat-developer-rhdh-main-e2e-ocp-v4-20-helm-nightly`
 - `-r / --repo`: Image repository (**required** for CLI mode — without it the script enters interactive mode)
 - `-t / --tag`: Image tag (e.g., `1.9`, `next`)
 - `-s / --skip-tests`: Deploy only, skip test execution (useful when you want to run tests manually afterward)
 
-Do NOT use shortened job names like `nightly-ocp-helm` for `-j` — these do not match the glob patterns in `openshift-ci-tests.sh`.
+**WARNING**: Do NOT use shortened job names like `nightly-ocp-helm` for `-j` — these do not match the glob patterns in `openshift-ci-tests.sh`.
 
 ### Image Selection
 
-Match the image repo and tag to the release branch:
-
-| Release branch | `-r` (image repo) | `-t` (image tag) |
-|---------------|-------------------|-------------------|
-| `main` | `rhdh-community/rhdh` | `next` |
-| `release-1.9` | `rhdh/rhdh-hub-rhel9` | `1.9` |
-| `release-1.8` | `rhdh/rhdh-hub-rhel9` | `1.8` |
+Refer to the `e2e-fix-workflow` rule for the release branch to image repo/tag mapping table.
 
 ### Deploy-Only Mode
 

.claude/skills/diagnose-and-fix/SKILL.md

@@ -12,6 +12,16 @@ Analyze the root cause of a failing E2E test and implement a fix following RHDH
 
 Use this skill after reproducing a failure (via `reproduce-failure`) when you have confirmed the test fails and need to determine the root cause and implement a fix.
 
+## IMPORTANT: Try the Playwright Healer Agent First
+
+**For locator drift and timing/race condition failures (categories 1 and 2 below), always invoke the Playwright healer agent BEFORE doing manual investigation.** The healer can run the test, inspect the live UI, generate correct locators, and edit the code — often resolving the issue end-to-end without manual intervention.
+
+```
+@playwright-test-healer Fix the failing test in playwright/e2e/plugins/<plugin>/<spec-file>.spec.ts
+```
+
+Only proceed with manual diagnosis if the healer agent cannot resolve the issue (e.g., the failure involves data dependencies, platform-specific behavior, or deployment configuration problems).
+
 ## Failure Pattern Recognition
 
 ### 1. Locator Drift
@@ -21,8 +31,8 @@ Use this skill after reproducing a failure (via `reproduce-failure`) when you ha
 **Cause**: The UI has changed and selectors no longer match.
 
 **Fix approach**:
-- Use the Playwright healer agent (`@playwright-test-healer`) to replay the test, inspect the current UI via page snapshots, and generate updated locators
-- Update to semantic selectors (see Coding Conventions below)
+- Invoke the Playwright healer agent (`@playwright-test-healer`) — it will replay the test, inspect the current UI via page snapshots, generate updated locators, and edit the code automatically
+- If the healer cannot resolve it, manually update to semantic role-based locators (see project rules)
 - Verify the updated locator works by re-running the test
 
 ### 2. Timing / Race Condition
@@ -32,7 +42,8 @@ Use this skill after reproducing a failure (via `reproduce-failure`) when you ha
 **Cause**: Test acts before the UI is ready, or waits are insufficient.
 
 **Fix approach**:
-- Replace `page.waitForTimeout()` with proper waits: `expect(locator).toBeVisible()`, `page.waitForLoadState()`
+- Invoke the Playwright healer agent first — it can identify timing issues by stepping through the test and observing UI state transitions
+- If manual fixes are needed: replace `page.waitForTimeout()` with proper waits: `expect(locator).toBeVisible()`, `page.waitForLoadState()`
 - Use `expect().toPass()` with retry intervals for inherently async checks:
   ```typescript
   await expect(async () => {
@@ -123,96 +134,9 @@ Use `@playwright-test-planner` when you need to understand a complex user flow b
 
 Use `@playwright-test-generator` when a test needs major rework and you need to generate new test steps from a plan.
 
-## RHDH Project Coding Conventions
-
-### Locator Best Practices
-
-**Always use semantic (role-based) locators** from `e2e-tests/playwright/support/selectors/semantic-selectors.ts`:
-
-```typescript
-// GOOD - semantic selectors
-page.getByRole('button', { name: 'Create' })
-page.getByRole('heading', { name: 'Catalog' })
-page.getByRole('link', { name: 'API' })
-page.getByRole('tab', { name: 'Overview' })
-page.getByLabel('Search')
-page.getByText('No results found')
-
-// BAD - CSS class selectors (deprecated)
-page.locator('.MuiButton-root')
-page.locator('[data-testid="catalog-page"]')
-page.locator('#search-input')
-```
-
-Use `SemanticSelectors` helper class methods:
-```typescript
-import { SemanticSelectors } from '../support/selectors/semantic-selectors';
-
-// Table interactions
-SemanticSelectors.getTableRow(page, 'my-entity')
-SemanticSelectors.getButton(page, 'Create')
-```
-
-### Page Object Model
-
-- Page classes live in `e2e-tests/playwright/support/pages/`
-- Selectors live in `e2e-tests/playwright/support/page-objects/`
-- Use existing page helpers: `UIhelper`, `Common`, `APIHelper`, `KubeClient`
-
-### Component Annotations
-
-Every spec file must have a component annotation:
-
-```typescript
-test.beforeAll(async ({}, testInfo) => {
-  testInfo.annotations.push({
-    type: 'component',
-    description: 'your_component_name',
-  });
-});
-```
-
-### Utility Classes
-
-- **`Common`** (`utils/common.ts`): Login flows, `waitForLoad()`, `signOut()`, `setupBrowser()`
-- **`UIhelper`** (`utils/ui-helper.ts`): 90+ UI interaction methods (click, verify, navigate)
-- **`APIHelper`** (`utils/api-helper.ts`): GitHub API, Backstage catalog API
-- **`KubeClient`** (`utils/kube-client.ts`): K8s resource management
-- **`RHDHDeployment`** (`utils/authentication-providers/rhdh-deployment.ts`): RHDH deployment lifecycle
-
-### Conditional Test Skipping
-
-```typescript
-import { skipIfJobName, skipIfJobType, skipIfIsOpenShift } from '../utils/helper';
-import * as constants from '../utils/constants';
-
-// Skip on specific platforms
-skipIfJobName(constants.GKE_JOBS);
-skipIfJobName(constants.AKS_JOBS);
-
-// Skip on PR jobs (presubmit)
-skipIfJobType('presubmit');
-
-// Skip on non-OpenShift
-skipIfIsOpenShift('false');
-```
-
-### Retry Patterns for Flaky Assertions
-
-```typescript
-// Use expect().toPass() for inherently async operations
-await expect(async () => {
-  await page.reload();
-  await expect(page.getByText('entity-name')).toBeVisible();
-}).toPass({ intervals: [2000, 5000, 10000], timeout: 60_000 });
-```
-
-### Forbidden Patterns
+## Coding Conventions
 
-- **Never** use `page.waitForNetworkIdle()` or `networkidle` — it's deprecated and unreliable
-- **Never** use raw CSS class selectors (`.MuiButton-root`) — use semantic selectors
-- **Avoid** `page.waitForTimeout()` for synchronization — use proper waits
-- **Never** hardcode secrets or credentials in test files
+Follow the coding conventions defined in the project rules (`playwright-locators`, `ci-e2e-testing`). Key points: use semantic role-based locators, include component annotations in every spec file, never use CSS class selectors or `waitForNetworkIdle()`.
 
 ## Cross-Repo Investigation