test-generation

Files (8)

• DOCS.md
• SKILL.md
• test.jest.tpl · jest_templates/
• manifest.yaml
• test.e2e.tpl · playwright_templates/
• __init__.py · scripts/
• main.py · scripts/
• test_skill.py · tests/

SKILL.md (first lines)

# test-generation

Produce a layered test strategy (unit/integration/e2e) and starter stubs for the
given modules across pytest, jest, and playwright.

## When to use
When establishing or improving test coverage. Triggers: *generate tests, test
plan, coverage plan, test scaffolding*.

## Inputs
- `modules` (array of strings, required).
- `frameworks` (array, optional, default `[pytest, jest, playwright]`).

## Outputs
- `test_plan_markdown` — pyramid, coverage matrix, targets.
- `stubs` — starter tests per module per framework.

## How it works
Builds a coverage matrix for the modules and emits idiomatic stubs per requested
framework from the templates in `jest_templates/` and `playwright_templates/`.

## User stories
- *As an engineer*, I get a coverage plan and runnable stubs to fill in.

## Edge cases
- A single module string is accepted.
- Empty modules → clear error.
- Unknown frameworks are ignored gracefully.

## Files
See [DOCS.md](DOCS.md).

From sarveshtalele/mcp-skills-registry, MIT.

More from sarveshtalele/mcp-skills-registry