slate-ar-gate

Runs repeated test, typecheck, and browser gate loops for Slate editor behavior verification.

16.5k|997|Updated Dec 2, 2019
One-click install
npx skills add https://github.com/udecode/plate --skill slate-ar-gate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slate-ar-gate
Source: https://github.com/udecode/plate/tree/main/.agents/skills/slate-ar-gate
Command: npx skills add https://github.com/udecode/plate --skill slate-ar-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifying that existing Slate editor proof surfaces (tests, typechecks, Playwright browser suites) pass repeatably requires disciplined execution, timing measurement, and failure logging, which is tedious and error-prone to do by hand.

Core Features & Use Cases

  • Repeated Gate Execution: Runs existing gate commands (bun check, package tests, Playwright suites) in a measured loop with elapsed-seconds metrics.
  • Pass/Fail Logging: Records statuses such as measure, keep, checks_failed, crash, and discard, plus duration metrics and dashboard state.
  • Failure Routing: Detects repeated failure signatures and hands off to the right owner (slate-patch for correctness bugs, slate-plan for design issues, slate-ar-perf for optimization).
  • Use Case: After modifying editor navigation behavior, run the full Playwright navigation and typing suites repeatedly to confirm the proof surface passes consistently and capture flake evidence.

Quick Start

Ask the agent to run the slate-ar-gate loop on the full editor behavior suite and report pass/fail status with timing metrics.

Frequently Asked Questions about slate-ar-gate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I repeatedly run Playwright editor behavior tests?

Run the gate loop with a focused Playwright command such as bun playwright on a specific integration suite with PLAYWRIGHT_RETRIES=0, then broaden to full suites. The loop logs each run's status and elapsed seconds for repeatability evidence.

What does the slate-ar-gate skill do?

It runs existing test, typecheck, and browser gate commands in a measured loop, logging pass/fail status, crashes, flakes, and duration metrics. It does not design new tests or fix correctness bugs itself.

When should a failing gate be routed to slate-patch?

Route to slate-patch when a gate fails twice with the same behavioral signal and the command shape is valid. The gate loop should not spin forever on a persistent failure.

Can this gate loop design missing tests for editor behavior?

No, missing oracle and test design belong to the testing, tdd, and editor-test-harvester skills. This gate only executes proof surfaces that already exist or have an obvious command.

What statuses are logged during a gate run?

Statuses include measure for passing runs, keep for passes after a useful change, checks_failed for assertion failures, crash for infra or runtime crashes, and discard for slower or noisier proofs with no value.