iblai

E2e Coverage — Testing skill for Claude Code

Testing community

Analyze recent code changes and sync the e2e test coverage.

How to install E2e Coverage

Installs to ~/.claude/commands/iblai-os-e2e-coverage.md

Terminal

mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/iblai/os/HEAD/.claude/commands/e2e-coverage.md -o ~/.claude/commands/iblai-os-e2e-coverage.md

Restart Claude Code, or start a new session, for it to be picked up.

What E2e Coverage does

Analyze recent code changes and sync the e2e test coverage. Follow these steps:

**Identify what changed**: Run `git diff main --name-only` (or `git diff HEAD~1 --name-only` if on main) to find modified files. Focus on files in `app/`, `components/`, `hooks/`, `lib/`, and `providers/` — these affect user-facing behavior.
**Run the coverage checker**: Execute `node e2e/scripts/check-journey-coverage.mjs --no-regress` to identify coverage gaps and regressions. Review its output carefully.

Alternatives in Testing

Create E2e — Create a Playwright E2E test with explicit success criteria 335 ★
Test After Change Diagnostics.V1 — If any program code changes, run unit-tests and follow up on the test-result (fix code if there is an error) 272 ★
M Merge Branch — Auto Merge Workflow: Analyze, Merge, Resolve, Test, Commit 139 ★