auto-qa-changes

Automates visual UI testing via a headless browser and HTTP API commands.

213|13|Updated Aug 7, 2025
One-click install
npx skills add https://github.com/imbue-ai/sculptor --skill auto-qa-changes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-qa-changes
Source: https://github.com/imbue-ai/sculptor/tree/main/.claude/skills/auto-qa-changes
Command: npx skills add https://github.com/imbue-ai/sculptor --skill auto-qa-changes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, and includes scripts (resource) components.

What problem does it solve?

This Skill automates visual UI testing within Sculptor, enabling users to perform end-to-end testing with real Claude and verify UI changes programmatically.

Core Features & Use Cases

  • Headless Browser Testing: Automate manual testing by controlling Sculptor's backend with a headless Chromium browser.
  • HTTP API Interaction: Send commands via curl, capture screenshots, and inspect UI states programmatically.
  • Use Case: Ideal for automating QA processes in web applications, allowing for efficient visual verification of UI changes without manual intervention.

Quick Start

Start the live browser server with the command 'uv run --project sculptor python -m sculptor.testing.manual_test_server --screenshots-dir "$SCREENSHOTS_DIR"'. Use curl to send commands and retrieve screenshots.

Frequently Asked Questions about auto-qa-changes

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

FAQPage Schema
How do I automate visual UI testing for web applications without manual checks?

Automate visual UI testing by controlling a headless Chromium browser via HTTP API commands, capturing screenshots to programmatically verify UI states and changes. This enables efficient end-to-end testing without manual intervention.

How does headless browser control work for end-to-end testing?

Headless browser control executes automated QA commands against a backend server using a headless Chromium instance. It captures screenshots and retrieves UI state data programmatically to validate visual changes and user flows without a visible browser window.

Do I need Playwright installed to run automated UI tests with this approach?

Yes, Playwright and a Chromium browser are required dependencies for headless execution. They provide the underlying browser automation framework needed to control the application backend and capture visual UI testing screenshots.

Can I use curl commands to inspect UI states during automated testing?

Yes, you can use curl to send HTTP API commands to the testing server, capturing screenshots and inspecting UI states programmatically. This allows you to automate QA processes and verify visual UI changes through HTTP requests.

What is the best way to verify UI changes programmatically in a desktop application?

The best way to verify UI changes programmatically is by running a live browser server and using headless Chromium to automate interactions. You capture screenshots and inspect UI states via HTTP API commands to validate visual updates.

Are there limitations when using headless Chromium for visual regression testing?

Headless Chromium visual regression testing requires a running live browser server and relies on Playwright for execution. It is limited to automating QA processes and capturing UI states via HTTP API commands rather than rendering visible browser windows.