final-qa-launcher

Start a development server and generate a QA checklist for pre-pull request verification.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/christian-byrne/ticket-to-pr-pipeline --skill final-qa-launcher
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: final-qa-launcher
Source: https://github.com/christian-byrne/ticket-to-pr-pipeline/tree/main/skills/final-qa-launcher
Command: npx skills add https://github.com/christian-byrne/ticket-to-pr-pipeline --skill final-qa-launcher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the final Quality Assurance process by automating the setup of the development environment and guiding manual verification before creating a Pull Request.

Core Features & Use Cases

  • Automated Dev Server Startup: Launches the development server in a background tmux session, configurable for different feature sets (standard, cloud, electron).
  • QA Checklist Generation: Creates a comprehensive checklist based on ticket acceptance criteria and local implementation plans.
  • Guided Verification: Prompts the user to manually verify the application against the generated checklist and handles reporting of issues or approval.
  • Use Case: Before merging code, use this Skill to ensure the development server is running correctly, all acceptance criteria are met, and the implementation aligns with the plan, catching potential bugs early.

Quick Start

Use the final-qa-launcher skill to start the dev server and generate a QA checklist for the current branch.

Frequently Asked Questions about final-qa-launcher

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

FAQPage Schema
How do I generate a QA checklist from ticket acceptance criteria before a pull request?

To generate a QA checklist before a pull request, this Skill compiles ticket acceptance criteria and local implementation plans, prompting you to manually verify application functionality against the compiled list.

Can I launch a dev server in the background for QA testing?

Yes, you can launch a dev server for QA testing in a background tmux session. The Skill initiates the server startup, polls for readiness, and manages the server lifecycle during verification.

Does the QA checklist support different feature sets like cloud or electron?

The automated dev server startup supports different feature sets, allowing you to configure the background tmux session for standard, cloud, or electron environments during QA verification.

What is the best way to verify local implementation details against a plan before merging code?

The best way to verify implementation details is using guided verification. This Skill orchestrates local code checkout, compiles data from a local plan.md, and handles your responses for issue reporting or approval.

How does the Skill handle issue reporting during manual verification?

During manual verification, the Skill handles issue reporting by prompting you to report issues, defer verification, or approve the checklist, managing the development server lifecycle based on your responses.

Do I need local ticket data to run pre-pull request verification?

Yes, you need local ticket data and a local plan.md file. The Skill compiles acceptance criteria from the ticket data and implementation details from the plan to guide the manual verification process.