test-gate
/test-gate
Run and supervise quality gates (lint, typecheck, unit, DB, build, e2e) in JS/TS projects that use Playwright or Cypress with Vitest or Jest, and leave machine-readable evidence. Use when asked to run, re-run or fix \"the gate\" or an e2e suite, to diagnose flaky or slow e2e tests, to write or review e2e specs (login, waiting, hydration), or to brief or supervise another agent that runs tests. Enforces one full run per gate, per-step time caps, login-once auth, signal-based waits and no weakened tests. Not for writing a unit test for one function, fixing a type or lint error, or general debugg
- Author
- AndresDiagoM ↗
- Repository
- agent-testing-skills ↗
- Licence
- Apache-2.0
- Last repository change
- 12.11.2026
Assessment and security
- Files in this package
- 36
- Scripts
- 19
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
- 19 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: assets/kit/app/build-id.ts, assets/kit/app/health-route.ts, assets/kit/app/hydration-marker.tsx, assets/kit/app/page-ready.tsx, assets/kit/app/with-page-ready.tsx, assets/kit/e2e/auth.setup.ts, assets/kit/e2e/goto-ready.ts, assets/kit/e2e/playwright.config.snippet.ts
What it does and when to use it
Run and supervise quality gates (lint, typecheck, unit, DB, build, e2e) in JS/TS projects that use Playwright or Cypress with Vitest or Jest, and leave machine-readable evidence. Use when asked to run, re-run or fix \"the gate\" or an e2e suite, to diagnose flaky or slow e2e tests, to write or review e2e specs (login, waiting, hydration), or to brief or supervise another agent that runs tests. Enforces one full run per gate, per-step time caps, login-once auth, signal-based waits and no weakened tests. Not for writing a unit test for one function, fixing a type or lint error, or general debugg
Triggers from the description
Original author description
Run and supervise quality gates (lint, typecheck, unit, DB, build, e2e) in JS/TS projects that use Playwright or Cypress with Vitest or Jest, and leave machine-readable evidence. Use when asked to run, re-run or fix \"the gate\" or an e2e suite, to diagnose flaky or slow e2e tests, to write or review e2e specs (login, waiting, hydration), or to brief or supervise another agent that runs tests. Enforces one full run per gate, per-step time caps, login-once auth, signal-based waits and no weakened tests. Not for writing a unit test for one function, fixing a type or lint error, or general debugg
How it works
- Rules (in order)
- Steps
- References (read only what the task needs)
SKILL.md preview
--- name: test-gate description: "Run and supervise quality gates (lint, typecheck, unit, DB, build, e2e) in JS/TS projects that use Playwright or Cypress with Vitest or Jest, and leave machine-readable evidence. Use when asked to run, re-run or fix \"the gate\" or an e2e suite, to diagnose flaky or slow e2e tests, to write or review e2e specs (login, waiting, hydration), or to brief or supervise another agent that runs tests. Enforces one full run per gate, per-step time caps, login-once auth, signal-based waits and no weakened tests. Not for writing a unit test for one function, fixing a type or lint error, or general debugging." license: Apache-2.0 compatibility: "Node 20+ for the optional kit; any package manager" --- # Test Gate Repo rules (`AGENTS.md`, `CLAUDE.md`, `OVERRIDES.md`) win over this skill. ## Rules (in order) 1. Read the repo rules and `package.json` scripts first. Never invent commands. 2. Evidence or it did not happen: each gate leaves command, exit code, duration and counts in `.gate/last.json` (or pasted raw output). "Tests pass" in prose counts for nothing; a reviewer re-runs. 3. One full run per gate. On failure fix, re-run only the failing file, then one final full run. 4. Never split a suite into batches or add sleeps. A rate limit or flake is a bug in the test setup: fix the cause. 5. Every step has a time cap and the gate stops at the first failure. Past ~30 min the supervisor reads the log; it does not wait. 6. Log in once (setup project + `storageState`, or `cy.session`). Only the auth spec uses the login UI. Specs that write data get their own user. Sign out with local scope. 7. Wait on signals, never on time: no `networkidle`, `waitForTimeout` or `toPass` for UI. Navigate through a ready helper. 8. Fix a flaky test at its cause. Never add retries (keep them at 0), broader locators, removed or negated assertions, `skip`/`fixme` or longer timeouts to get green. 9. A skip needs approval from the user or the orchestrator (never the agent writing it), a linked issue and an evidence entry. 10. Use a free port, check the served build id against the build on disk, kill only processes you started. 11. On Windows use the installed Chrome (`channel: 'chrome'`) and one worker; 2+ Playwright-bundled Chromium stall. 12. Builders run their own e2e for what they touched before reporting. A spec never run is not delivered. 13. No literal secrets, not even fake ones, and no destructive commands in tests, examples or briefs. Generate values at run time. 14. Delegating or supervising: use the brief template in `references/supervision.md`. An agent's report is not evidence. ## Steps 1. Detect the package manager (`packageManager` field, then lockfile) and resolve each step from `scripts`. 2. Plan the steps (lint, typecheck, unit, db, build, e2e) with caps; report any missing script, do not guess. 3. Run each step once, fail fast, keep its log under `.gate/logs/`. 4. Write the evidence file (`complete` is true only if every required step ran and passed or has an approved skip). 5. Report wall time, passed/failed/skipped per suite, skips and the evidence path. ## References (read only what the task needs) | Task | File | |---|---| | Running or designing a gate, scripts, caps, no-kit mode | `references/gate-run.md` | | Writing or reading `.gate/last.json` | `references/evidence-schema.md` | | Login, storageState, per-spec users, logout | `references/e2e-auth.md` | | Writing specs, hydration, intermittent failures | `references/e2e-waiting.md` | | Flaky, red or about-to-skip test | `references/flaky-and-skips.md` | | Servers, ports, builds, Windows, WSL | `references/servers-builds-windows.md` | | Briefing or watching another agent | `references/supervision.md` | | Repo has its own rules or a third-party testing skill | `references/repo-rules-overrides.md` | | Cypress or Jest project | `references/cypress-jest.md` | | Which versions each tip was checked against | `references/versions.md` |
Files in this package (36)
- SKILL.md 4 KB
- assets/kit/e2e-changed.map.json 1 KB
- assets/kit/evidence.schema.json 5 KB
- assets/kit/install.mjs 17 KB
- assets/kit/kit.config.example.json 4 KB
- assets/kit/app/build-id.ts 1 KB
- assets/kit/app/health-route.ts 1 KB
- assets/kit/app/hydration-marker.tsx 1 KB
- assets/kit/app/page-ready.tsx 2 KB
- assets/kit/app/with-page-ready.tsx 1 KB
- assets/kit/e2e/README.md 2 KB
- assets/kit/e2e/auth.setup.ts 6 KB
- assets/kit/e2e/goto-ready.ts 3 KB
- assets/kit/e2e/playwright.config.snippet.ts 5 KB
- assets/kit/e2e/preflight.ts 3 KB
- assets/kit/hooks/settings.snippet.json 1 KB
- assets/kit/hooks/stop-gate.mjs 19 KB
- assets/kit/scripts/e2e-changed.mjs 13 KB
- assets/kit/scripts/e2e-guard.mjs 19 KB
- assets/kit/scripts/gate-lib.mjs 47 KB
- assets/kit/scripts/gate-lib.test.mjs 35 KB
- assets/kit/scripts/gate.mjs 18 KB
- assets/kit/scripts/guard-core.mjs 61 KB
- assets/kit/scripts/guard.test.mjs 23 KB
- assets/kit/scripts/kit-tools.test.mjs 24 KB
- assets/kit/scripts/fixtures/reference-v1-last.json 1 KB
- references/cypress-jest.md 2 KB
- references/e2e-auth.md 4 KB
- references/e2e-waiting.md 3 KB
- references/evidence-schema.md 4 KB
- references/flaky-and-skips.md 4 KB
- references/gate-run.md 5 KB
- references/repo-rules-overrides.md 4 KB
- references/servers-builds-windows.md 4 KB
- references/supervision.md 4 KB
- references/versions.md 3 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · AndresDiagoM/agent-testing-skills | 100 | Apache-2.0 |
| AndresDiagoM/agent-testing-skills | 100 | Apache-2.0 |
| emaballarin/ccplugins | 90 | MIT |
Database snapshot: 13.11.2026 · package version 1dafa8646548 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100run-tests
Stage 4 (Test) - automatically run build, typecheck, lint and Vitest unit tests for the app on the feature branch, set them up if missing, map results to spec requirements and write test-report.md. Use after a build/PR, when the user says "run the tests", "verify this", "is it… - 100test-generator
Generate unit, integration, and end-to-end tests for existing code. Use when a user asks to write tests, add test coverage, create unit tests, generate integration tests, build e2e tests, improve code coverage, write specs, or add testing to a project. Supports Jest, Vitest,… - 100cypress-cloud-cli
Runs the cy-cloud CLI to inspect Cypress Cloud organizations, projects, runs, specs, tests, failure screenshots, and Test Replay data. Use when the user mentions Cypress Cloud, cy-cloud, cypress-cloud-cli, a Cloud run or test URL, failing or flaky Cypress tests, Test Replay, run… - 90quality-e2e-testing
Use this skill when setting up E2E testing, end-to-end tests, Playwright, Cypress, browser tests, user flow tests, or integration tests. This skill enforces: framework selection (Playwright preferred), page object model, test isolation, parallel execution, CI integration, and… - 100proof-e2e
Build E2E test specs for critical user journeys — Playwright or Cypress, page objects, setup/teardown, CI config. Use when asked to "write E2E tests", "end-to-end testing", "browser tests", "UI tests", or "Playwright tests". - 100proof-e2e
Build E2E test specs for critical user journeys — Playwright or Cypress, page objects, setup/teardown, CI config. Use when asked to "write E2E tests", "end-to-end testing", "browser tests", "UI tests", or "Playwright tests".