Skip to content
SkillMixed728 tokens in use

replica-test

Tests an app clone end to end: a test plan from the recon flows, Playwright and axe specs, manual click-throughs and severity-rated bug reports.

10,140 stars on the repository MIT LicenseJakeschincariol/replica-skill · replica-test
/plugin install replica-skill@replica-skill
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing replica-test costs

111tokens idle
728tokens in use
1,068tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Mixed

Script-ledMixedModel-led

Scripts do part of the work and the model's judgement does the rest.

This describes the skill's structure, how much of it is scripts. It does not say how well it works. Scripts: e2e.example.spec.ts.

Touches

shelldetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter12/15
  • Structure17/25
  • Examples9/15
  • Output10/15
  • Size15/15
  • Resources15/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent
  • Runs shell commands−5

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 48

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Needs attention
  • Development activity32
  • Maintenance4
  • Community64
  • Maturity12
  • Momentum40

replica-test builds a test plan from the flows in the recon map, with numbered happy, edge and negative cases, and automates what it can with Playwright specs that fail on console errors, server errors and accessibility violations.

What cannot be automated gets a manual pass. Bugs are written in a fixed format with severity S1 to S4, exact steps and evidence, and fixed test-first.

What You Get

  • A numbered test plan such as F01-H1 and F01-E3 covering happy, edge and negative cases
  • One Playwright spec per flow using role and label selectors, with console, 5xx and axe checks
  • A manual checklist or browser-driven pass for email, OAuth, payments and visual glitches
  • A replica/bugs.md of reproduced bugs with severity, steps, expected, actual and evidence
  • A fix loop: failing test first, fix, pass, keep the test

Common Use Cases

  • Writing end-to-end tests for each flow of a new app
  • Running an edge-case sweep for time zones, double submit, expired sessions and second-user data
  • Gating a release on no open S1 or S2 bugs

What Makes It Unique

It carries a fixed edge-case checklist applied to every flow, uses severity definitions that tie S1 to data loss, security and payments, and reports only what was reproduced, keeping speculation in a separate to-check list. It also forbids load or fuzz testing of the original app’s servers.

Under The Hood

The skill is instructions plus a test plan template, a bug report template and an example Playwright spec. The agent runs shell commands: it installs Playwright and the axe package with npm, installs a Chromium browser, and runs the test suite against your local dev server. It writes spec files and markdown reports into your project and may drive a browser to screenshot steps. It uses Stripe test cards for declined-payment cases.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers