analyze-test-codebase

Analyze Playwright codebases to report conventions, configuration, and patterns.

4|1|Updated Feb 3, 2026

Search Tags:#codebase #configuration #patterns #playwright #report #analyze #tests

Ready to run

npx skills add https://github.com/lespaceman/athena-workflow-marketplace --skill analyze-test-codebase

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: analyze-test-codebase
Source: https://github.com/lespaceman/athena-workflow-marketplace/tree/main/plugins/playwright-automation/skills/analyze-test-codebase
Command: npx skills add https://github.com/lespaceman/athena-workflow-marketplace --skill analyze-test-codebase

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scans and analyzes an existing Playwright test codebase to understand its conventions, configuration, and patterns before writing new tests. It outputs a structured report that helps engineers plan improvements without modifying tests or running live apps.

Core Features & Use Cases

Locate Playwright configuration files (playwright.config.ts, playwright.config.js, or playwright.config.mjs) across the project.
Extract configuration details such as baseURL, testDir, projects, use options (viewport, headless, trace, screenshot), webServer, and globalSetup/globalTeardown.
Scan the test directory structure to count tests, identify naming conventions, and understand organization strategies.
Detect common testing patterns (locator strategies, wait strategies, test structure, data management, Page Objects, auth handling, and custom fixtures).
Check for supporting infrastructure like fixtures, pages, environment files, CI configs, npm scripts, HARs, and snapshots to inform coverage.

Quick Start

Run this skill from the project root to generate a concise report of your Playwright setup.

Frequently Asked Questions about analyze-test-codebase

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

FAQPage Schema

How do I audit an existing Playwright test codebase for conventions and patterns?▼

Scanning a Playwright test codebase locates configuration files, extracts settings like baseURL and projects, and identifies testing patterns. This generates a structured report detailing conventions, directory structure, and supporting infrastructure for quick decision-making.

What Playwright configuration details are extracted during a codebase analysis?▼

A Playwright configuration analysis extracts baseURL, testDir, projects, use options such as viewport and headless, webServer, and globalSetup or globalTeardown settings. It verifies these core configuration fields to document the project's current testing setup.

Does the analysis detect common Playwright testing patterns like Page Objects and custom fixtures?▼

Yes, the analysis detects common Playwright testing patterns including locator strategies, wait strategies, data management, Page Objects, auth handling, and custom fixtures. It scans the test directory to identify these patterns and understand organization strategies.

Can I check for supporting infrastructure like CI configs and environment files in my Playwright project?▼

You can check for supporting infrastructure by scanning the project for fixtures, pages, environment files, CI configs, npm scripts, HARs, and snapshots. This informs test coverage and provides a complete view of the supporting test infrastructure.

What is the best way to summarize test directory structure and naming conventions in Playwright?▼

The best way to summarize a Playwright test directory structure is to scan and count tests, identify naming conventions, and understand organization strategies. This produces a concise report of the test setup without modifying tests or running the live app.