analyzing-e2e-tests

Analyze Playwright/Cypress E2E tests to generate structured documentation.

9|Updated Jan 15, 2026

Search Tags:#automation #documentation #e2e #playwright #ci #tests

Ready to run

npx skills add https://github.com/cliftonc/unwind --skill analyzing-e2e-tests

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: analyzing-e2e-tests
Source: https://github.com/cliftonc/unwind/tree/main/skills/analyzing-e2e-tests
Command: npx skills add https://github.com/cliftonc/unwind --skill analyzing-e2e-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze end-to-end tests including browser automation, API workflows, and full system testing to produce structured, navigable documentation that can guide rebuilding or auditing test suites.

Core Features & Use Cases

Clear, machine-readable documentation layout for tests including index.md, config.md, page-objects.md, fixtures.md, and flows.md.
Supports feature-based split in large codebases to keep documentation modular and maintainable.
Follows an incremental-write workflow that documents findings progressively and updates the index as sections are completed.

Quick Start

Initialize the e2e-tests docs folder and begin with an index.md that summarizes test areas and marks sections as pending until details are written.

Frequently Asked Questions about analyzing-e2e-tests

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

FAQPage Schema

How do I generate structured documentation for Playwright E2E tests?▼

Generate structured E2E test documentation by analyzing browser automation workflows and configs to produce navigable files like index.md, page-objects.md, and fixtures.md. This process organizes test suites into a machine-readable format under a dedicated docs folder.

What is the best way to document Cypress test suites for large codebases?▼

The best way to document Cypress test suites is using a feature-based split approach. This keeps documentation modular and maintainable by progressively writing findings into specific files and updating a central index as sections are completed.

Does this approach support incremental writes for E2E test documentation?▼

Yes, this approach supports incremental writes for E2E test documentation. It documents findings progressively and updates the index as sections are completed, allowing you to initialize the docs folder and mark sections as pending until details are written.

How do I audit user flows and page objects across CI pipelines?▼

Audit user flows and page objects across CI pipelines by analyzing end-to-end tests to extract full system testing workflows. This produces structured documentation covering configs, fixtures, and flows to guide rebuilding or auditing test suites.

Can I use this to analyze API workflows alongside browser automation tests?▼

Yes, you can analyze API workflows alongside browser automation tests. The process evaluates end-to-end tests including API workflows and full system testing to produce structured, navigable documentation of all integrated test layers.