eng-qa-bootstrap

Provisions isolated Compozy QA labs and emits canonical bootstrap manifests for downstream QA.

2.7k|171|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/compozy/compozy --skill eng-qa-bootstrap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eng-qa-bootstrap
Source: https://github.com/compozy/compozy/tree/main/.agents/skills/eng/eng-qa-bootstrap
Command: npx skills add https://github.com/compozy/compozy --skill eng-qa-bootstrap

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Setting up a consistent, isolated QA environment for Compozy (daemon, workspace, provider homes, ports, evidence scaffolding) is manual and error-prone, and downstream QA steps need a single canonical manifest to consume instead of reconstructing environment values by hand.

Core Features & Use Cases

  • Isolated Lab Provisioning: Creates or reuses a QA lab with its own workspace, COMPOZY_HOME, provider home, free HTTP port, and Unix-socket-safe runtime paths.
  • Canonical Manifest Emission: Writes bootstrap-manifest.json and bootstrap.env containing every env value, audit command, and teardown command downstream QA needs.
  • Playbook Seeding: When given a playbook ref, materializes agents, open tasks, knowledge files, and a behavioral charter into the lab workspace.
  • Mandatory Teardown: Ships a teardown script that stops the daemon, kills lab processes, and writes clean/dirty teardown evidence.
  • Use Case: Before running a release-candidate QA pass, invoke this Skill to spin up a fresh lab, receive the BOOTSTRAP_MANIFEST path, and hand it to downstream QA execution and reporting skills.

Quick Start

Ask the agent to bootstrap a QA lab for scenario 'release-candidate' using the eng-qa-bootstrap skill and report the emitted manifest path.

Frequently Asked Questions about eng-qa-bootstrap

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

FAQPage Schema
How do I bootstrap an isolated Compozy QA lab?

Run the bootstrap-qa-env.py script with a scenario slug and repo root, optionally passing a playbook ref or a targeted profile with required surfaces. It creates the lab workspace, provider home, and ports, then prints the BOOTSTRAP_MANIFEST path for downstream QA.

When should I reuse an existing QA lab manifest?

Reuse a lab only when continuing the same active QA session or loop, by passing the exact manifest path with --reuse-manifest. The helper health-checks the manifest and rebuilds a fresh lab if paths are missing or invalid.

What artifacts does the QA bootstrap manifest include?

The manifest records workspace and QA output paths, COMPOZY_HOME, HTTP port, UDS and tmux socket paths, provider homes, browser mode, scenario contract, behavioral charter, journey log, audit command, and teardown command.

How do I tear down a Compozy QA lab after a run?

Run teardown-qa-env.py with the manifest path on every terminal path, including pass, fail, blocked, or abort. It stops the daemon, kills lab processes and port listeners, and writes teardown.json; exit code 1 means survivors remain and is a blocking failure.

When should I not use the QA bootstrap skill?

Do not use it for unit tests, planning-only work, or browser-only checks, since it provisions full daemon, workspace, and provider infrastructure. It is intended only for QA passes that need a real isolated runtime environment.