Skip to content

/test-author

Testing class

Writes test source into the repo and executes it — the only class that does both. Shared rules: CONVENTIONS-testing.md.

Consumes /test-plan's case objects, emits specs for whatever framework the repo already uses (never a hardcoded one), enforces a data-testid locator contract and flags brittle selectors, and generates page objects from the detected app structure. Writes only inside detected test directories and PROPOSES the commit — it never runs git.

At a glance

Run it /test-author
Class testing
Version 0.1.0
Author navjyotnishant
Needs the repo's own test framework · /test-plan output · the app's markup or component source
Source skills/test-author/SKILL.md

What it needs, and what happens without it

Every tool is detected at runtime — none is installed for you.

Tool Without it
the repo's own test framework SKIP — never scaffold a framework, never pick one
/test-plan output ask for cases; do not invent a plan from the codebase
the app's markup or component source generate specs without page objects, and say so

Agents it spawns

This skill spawns no subagents — it runs inline.

The procedure

The executable steps live in the skill file itself and are deliberately not reproduced here: they are instructions to the model at runtime, not documentation.

Read test-author/SKILL.md →