Test

Generate and run scoped BE and FE tests with pytest, jest, vitest, or Go.

1|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/samdae/archflow --skill test-samdae
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Test
Source: https://github.com/samdae/archflow/tree/main/skills/test
Command: npx skills add https://github.com/samdae/archflow --skill test-samdae

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate and/or run tests with scoped targeting across BE (API/unit) and FE (Playwright headless E2E), reducing manual test planning time and increasing feedback speed.

Core Features & Use Cases

  • Scoped test generation and execution for backend and frontend changes.
  • Supports change-based diff scope, FR-based mapping, and module-based targeting.
  • Real-world use case: after modifying an API endpoint and related UI component, automatically generate and run relevant tests to validate behavior.

Quick Start

Invoke the test trigger to generate and/or run tests across BE and FE with default change-based scope. By default, tests are scoped to changes since the arch baseline. Use the interactive prompts to adjust target (BE/FE/Both), scope (change-based / FR-based / module-based), and mode (generate / run / both).

Frequently Asked Questions about Test

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

FAQPage Schema
How do I generate and run tests scoped to recent code changes?

Generate and run tests scoped to recent changes by using the change-based diff scope, which automatically targets testing to specific backend or frontend codebase parts modified since the baseline. This reduces manual test planning and speeds up feedback.

Can I use Playwright for headless E2E frontend test generation?

Playwright supports headless E2E frontend test generation and execution. The workflow targets frontend changes by generating and running Playwright tests, provided your project uses a conventional layout like an e2e/ directory.

Does this test automation workflow support pytest, jest, and vitest?

This test automation workflow supports pytest, jest, vitest, and Go test frameworks. It requires an existing test framework and a conventional project layout with a tests/ or e2e/ directory to guide template generation for backend API and unit tests.

What's the best way to target test generation for specific backend modules?

Target test generation for specific backend modules using module-based targeting or FR-based mapping. These scoping methods focus test generation on specific API endpoints and functional requirements rather than testing the entire codebase.

Do I need a specific project layout to generate backend and frontend tests?

You need a conventional project layout with a tests/ or e2e/ directory to generate backend and frontend tests. Optional profiles under profiles/be.md or profiles/fe.md can further guide template generation for your specific test framework.

Why are my generated tests not matching my project's test conventions?

Generated tests may not match conventions without optional profiles under profiles/be.md or profiles/fe.md. Creating these profile files guides template generation to align with your specific pytest, jest, or vitest framework configurations and project standards.