Run any Skill in Manus with one click

verify-e2e

Stars5

Forks0

UpdatedJuly 7, 2026 at 16:48

Reset and seed the local Supabase stack, then run the Playwright E2E suite (or a single spec) and summarize failures. Use when asked to verify end-to-end behavior.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

tum-ai

tum-ai/member-manager

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

SKILL.md

readonly

name	verify-e2e
description	Reset and seed the local Supabase stack, then run the Playwright E2E suite (or a single spec) and summarize failures. Use when asked to verify end-to-end behavior.

/verify-e2e

Run the E2E suite against a fresh seeded stack.

Reset the stack — pnpm supabase:reset (clean DB reset + seed), then pnpm setup:local.
Run — pnpm test:e2e for the full suite, or pnpm test:e2e e2e/<name>.spec.ts for a single spec if the user named one.
On failure — summarize which specs failed and the likely cause. Because E2E hits the real backend (no MSW), a failure usually points at a real route/seed/migration bug or a seed↔fixture drift (supabase/seed.sql ↔ e2e/fixtures ↔ e2e/helpers.ts).
Report the Playwright report path (playwright-report/) and a concise pass/fail summary. Suggest pnpm test:e2e:ui for interactive debugging if specs are flaky.

More from this repository

same repository

commit

tum-ai/member-manager

Stage the intended changes only, derive a scoped conventional-commit message, branch first if on main, run the staged lint check, and commit. Use when the user asks to commit work.

2026-07-075

gate

tum-ai/member-manager

Run the full pre-push gate (lint, typecheck, test, build) and triage any failures by stage. Use before pushing or when asked to verify the repo is green.

2026-07-075

new-feature

tum-ai/member-manager

Scaffold a new client feature folder following the Page→hook→sections pattern, using features/tools as the template. Use when starting a new client feature.

2026-07-075

pr-review

tum-ai/member-manager

Review a pull request against member-manager's invariants and post inline comments. Use when asked to review a PR.

2026-07-075

tumai-ci

tum-ai/member-manager

Use when changing UI, styling, theming, logos, imagery, or visual copy in this repo so the result follows the TUM.ai corporate identity. Apply the vendored brand guide, color system, typography, button treatment, and dark/light mode rules before shipping frontend work.

2026-03-305

name	verify-e2e
description	Reset and seed the local Supabase stack, then run the Playwright E2E suite (or a single spec) and summarize failures. Use when asked to verify end-to-end behavior.

/verify-e2e

Run the E2E suite against a fresh seeded stack.

Reset the stack — pnpm supabase:reset (clean DB reset + seed), then pnpm setup:local.
Run — pnpm test:e2e for the full suite, or pnpm test:e2e e2e/<name>.spec.ts for a single spec if the user named one.
On failure — summarize which specs failed and the likely cause. Because E2E hits the real backend (no MSW), a failure usually points at a real route/seed/migration bug or a seed↔fixture drift (supabase/seed.sql ↔ e2e/fixtures ↔ e2e/helpers.ts).
Report the Playwright report path (playwright-report/) and a concise pass/fail summary. Suggest pnpm test:e2e:ui for interactive debugging if specs are flaky.