pr-test

Automate end-to-end PR testing across docker-compose stacks, browser UI, and APIs.

Updated Jan 16, 2026
One-click install
npx skills add https://github.com/ghpworkuse-web/train --skill pr-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-test
Source: https://github.com/ghpworkuse-web/train/tree/main/AutoGPT/.claude/skills/pr-test
Command: npx skills add https://github.com/ghpworkuse-web/train --skill pr-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables reliable end-to-end testing of PRs and platform changes by orchestrating docker-compose stacks, browser automation, and API calls to validate PR behavior across the full stack.

Core Features & Use Cases

  • End-to-end PR validation across dockerized services, browser UI, and backend APIs
  • Generates and validates test evidence including screenshots, logs, and API responses
  • Useful for reviewing PR readiness and regression testing in feature branches

Quick Start

Trigger the test suite for a specific PR by passing the worktree path or PR number to the tool.

Frequently Asked Questions about pr-test

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

FAQPage Schema
How do I automate end-to-end PR testing across a dockerized stack?

End-to-end PR testing is automated by orchestrating docker-compose stacks, browser automation, and API calls to validate behavior across the full stack. This generates traceable test evidence including screenshots, logs, and API responses.

Can I use docker-compose to validate browser UI and backend API calls during integration testing?

Docker-compose is used to validate browser UI and backend API calls by spinning up the full stack and running automated interactions against it. This verifies PR behavior across all integrated services simultaneously.

What is the best way to capture screenshots and API responses as test evidence for a pull request?

Capturing screenshots and API responses for pull requests is handled by the automated test suite during execution. It generates comprehensive test artifacts to verify state and provide traceable evidence for PR readiness.

How do I trigger end-to-end tests for a specific feature branch or PR number?

Triggering end-to-end tests for a specific PR requires passing the worktree path or PR number to the testing tool. This initiates validation across the live stack for that particular feature branch.

Does browser automation work with docker-compose for regression testing in feature branches?

Browser automation works with docker-compose for regression testing by driving interactions against the dockerized UI. It validates feature branch changes and captures state verification artifacts throughout the test run.

When should I use automated end-to-end testing instead of manual integration testing?

Automated end-to-end testing applies to both manual and integration testing scenarios when you need traceable state verification. It is ideal for reviewing PR readiness and running regression tests across feature branches.