# Playwright Documentation Tests

> Automation-code documentation skill for Playwright suites. Use when Codex needs to add or improve human-readable comments, docblocks, or file-level explanations around existing Playwright tests without drowning the code in redundant commentary.

- Skill: `jovd83/playwright-documentation-tests` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add jovd83/playwright-documentation-tests`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jovd83/playwright-documentation-tests/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: jovd83 (https://skillmd.com/u/jovd83)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/jovd83/playwright-documentation-tests

---


# Playwright Automation Documentation

Use this skill to improve readability of existing Playwright code.

## Workflow

1. Read the target test file or support module first.
2. Identify where comments would materially help a future maintainer.
3. Add concise documentation at the file, suite, test, fixture, or helper level as appropriate.

## Commenting Rules

- Prefer high-signal docblocks over line-by-line narration.
- Explain intent, scope, or non-obvious behavior.
- Do not restate code that is already obvious from the test title or method name.
- Avoid comment spam in straightforward tests.

## Output

After editing, summarize:

- what was documented,
- why those locations mattered,
- any parts of the suite that are still hard to understand and may need refactoring rather than more comments.