finalrun-generate-test

Plan testing campaigns and generate FinalRun YAML artifacts from repository context.

298|35|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/final-run/finalrun-agent --skill finalrun-generate-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finalrun-generate-test
Source: https://github.com/final-run/finalrun-agent/tree/main/skills/finalrun-generate-test
Command: npx skills add https://github.com/final-run/finalrun-agent --skill finalrun-generate-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides QA engineers to plan testing campaigns and generate strict FinalRun YAML artifacts for tests and suites, streamlining test creation from repo context.

Core Features & Use Cases

  • Plan testing campaigns by feature and repository layout.
  • Locate existing test assets grouped by feature and propose organized plan.
  • Save approved tests in strict YAML format and validate configurations via finalrun check.

Quick Start

Ask me to generate FinalRun YAML artifacts for a repository, and I will plan tests, organize assets by feature, and save approved tests in strict YAML.

Frequently Asked Questions about finalrun-generate-test

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

FAQPage Schema
How do I generate FinalRun YAML test artifacts from my repository structure?

To generate FinalRun YAML test artifacts, the skill analyzes your repository structure and environment configuration to plan tests, organize assets by feature, and save approved configurations in strict YAML format.

What is needed to plan a testing campaign with FinalRun?

Planning a testing campaign with FinalRun requires the finalrun CLI installed on PATH, repository-derived app identity from .finalrun/config.yaml, and environment bindings in .finalrun/env/*.yaml.

Can I validate FinalRun test configurations before saving?

Yes, you can validate FinalRun test configurations using the finalrun check command to ensure strict YAML artifacts and environment bindings are correct before saving approved tests.

How does organizing test assets by feature work in FinalRun?

Organizing test assets by feature works by locating existing assets within your repository layout and proposing an organized plan that groups tests logically before generating strict YAML artifacts.

Does FinalRun work with environment configuration files for test generation?

Yes, FinalRun works with environment configuration files by relying on environment bindings defined in .finalrun/env/*.yaml alongside repository-derived app identity from .finalrun/config.yaml to generate tests.