autospec-e2e-clone

Provision isolated anonymized production clones for autospec-test E2E testing.

3|1|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/berlinguyinca/autospec --skill autospec-e2e-clone
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autospec-e2e-clone
Source: https://github.com/berlinguyinca/autospec/tree/main/skills/autospec-e2e-clone
Command: npx skills add https://github.com/berlinguyinca/autospec --skill autospec-e2e-clone

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires yq, ajv, python3, sqlite3, psql, mysql, docker, kubectl, aws, and includes scripts (resource) components.

What problem does it solve?

Provisioning reliable end-to-end test environments from production-like data is slow and risky, because teams need isolated clones, anonymized data, consistent scaling, and a stable URL for test execution.

Core Features & Use Cases

  • Isolated clone provisioning (Mode II): Creates a scaled-down anonymized clone of a production environment suitable for autospec-test E2E runs.
  • Declarative contract enforcement: Reads and validates .autospec/clone.yml to determine snapshot sources, anonymization rules, scaling behavior, and expose adapter settings.
  • PII-safe anonymization with fail-closed assertions: Redacts/hash/scrubs sensitive columns and can verify post-anonymization PII invariants.
  • FK-aware scale-down and reachability closure: Samples data while preserving referential integrity so E2E tests fail for real reasons, not missing rows.
  • Edge-case seed injection: Ensures required shape predicates have sufficient data by generating synthetic rows from a catalog (+ optional overlay).
  • Expose + health-gated URL output: Brings up the environment via the configured adapter and writes the resulting routable URL to .autospec/clone-url.txt.

Quick Start

Run /autospec-e2e-clone in your harness to provision .autospec/clone.yml and output a ready-to-test URL in .autospec/clone-url.txt.

Frequently Asked Questions about autospec-e2e-clone

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

FAQPage Schema
How do I provision an isolated E2E testing clone from production data?

You provision an E2E testing clone by defining snapshot sources and anonymization rules in a `.autospec/clone.yml` contract, which the workflow validates to create a scaled-down, isolated clone environment.

What is referential integrity aware scale-down for test environments?

Referential integrity aware scale-down is a data sampling method that preserves foreign key relationships, ensuring E2E tests fail from real application bugs rather than missing database rows.

How does PII anonymization work when cloning a production database?

PII anonymization works by redacting, hashing, or scrubbing sensitive columns based on declarative contract rules, and the workflow fails closed if post-anonymization PII assertions are not met.

Can I use this environment provisioning workflow with AWS S3 and PostgreSQL?

Yes, the environment provisioning workflow supports AWS S3 snapshotting and PostgreSQL databases, utilizing dependencies like `aws`, `psql`, `kubectl`, and `docker` to provision isolated test clones.

Do I need docker and kubectl to expose a routable URL for E2E tests?

Yes, you need `docker` and `kubectl` to bring up the environment via the configured expose adapter, which health-gates the deployment and writes the resulting routable URL to `.autospec/clone-url.txt`.

Why does my anonymized database clone fail closed during provisioning?

Your anonymized database clone fails closed during provisioning when contract validation fails or when post-anonymization PII assertions detect unredacted sensitive data, ensuring no unsafe environment is exposed.