pr-testing

Automate pull request testing by downloading and verifying the Aspire CLI.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/sast-playground/aspire --skill pr-testing-sast-playground
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-testing
Source: https://github.com/sast-playground/aspire/tree/main/.github/skills/pr-testing
Command: npx skills add https://github.com/sast-playground/aspire --skill pr-testing-sast-playground

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, aspire, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the testing of pull requests by downloading and testing the Aspire CLI from a PR build, verifying the version, and running test scenarios based on PR changes.

Core Features & Use Cases

  • PR Testing Automation: Automatically download and test the Aspire CLI from a PR build.
  • Version Verification: Ensures the installed CLI matches the PR's latest commit.
  • Test Scenario Generation: Generates test scenarios based on PR changes.
  • Test Execution: Executes the generated test scenarios.
  • Evidence Capture: Captures screenshots and logs for each test scenario.
  • Detailed Reporting: Generates a comprehensive report with PR information, CLI version verification, changes analyzed, test scenarios executed, and overall result.

Quick Start

Test PR 12345 with the pr-testing skill.

Frequently Asked Questions about pr-testing

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

FAQPage Schema
How do I automate pull request testing for Aspire CLI builds?

Automate pull request testing by downloading the Aspire CLI from a PR build, verifying the version matches the latest commit, and executing generated test scenarios based on PR changes.

Can I generate and run test scenarios based on code changes in a pull request?

Yes, you can generate test scenarios based on pull request changes and execute them automatically. The process captures screenshots and logs for each scenario to verify code quality.

How do I verify the installed CLI version matches a specific pull request commit?

Verify the installed CLI version by downloading the Aspire CLI directly from the PR build and checking it against the PR's latest commit to ensure version consistency.

Do I need GitHub API access and Aspire CLI to run PR testing automation?

Yes, you need GitHub API access and the Aspire CLI installed to execute PR testing automation. These dependencies are required to download builds and run test scenarios.

What's the best way to capture test evidence for pull request test scenarios?

Capture test evidence by executing generated test scenarios during PR testing, which automatically records screenshots and logs for each scenario into a comprehensive final report.

Why does PR testing require generating test scenarios from pull request changes?

Generating test scenarios from pull request changes ensures relevant code paths are validated. This targeted approach verifies code quality by focusing tests on the specific modifications introduced in the PR.