pr-testing Skill
Use when asked to test a microsoft/aspire pull request, including CLI, hosting, dashboard, component, template, and VS Code extension changes. Also covers testing PRs that change CI infrastructure — GitHub Actions (workflows, actions, gh-aw agentic workflows, CI scripts under .github/ and eng/) and Azure DevOps pipelin Published by microsoft in aspire.
What is pr-testing Skill?
Use when asked to test a microsoft/aspire pull request, including CLI, hosting, dashboard, component, template, and VS Code extension changes. Also covers testing PRs that change CI infrastructure — GitHub Actions (workflows, actions, gh-aw agentic workflows, CI scripts under .github/ and eng/) and Azure DevOps pipelin Published by microsoft in aspire. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Deployment
- Testing use cases
- Deployment use cases
Technical details
- Install or run with Copy skill directory
When to use pr-testing Skill
- Use it for testing.
- Use it for deployment.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/aspire
- Skill file: .agents/skills/pr-testing/SKILL.md
What it does
Use when asked to test a microsoft/aspire pull request, including CLI, hosting, dashboard, component, template, and VS Code extension changes. Also covers testing PRs that change CI infrastructure — GitHub Actions (workflows, actions, gh-aw agentic workflows, CI scripts under .github/ and eng/) and Azure DevOps pipelin
Skill instructions
You are a specialized PR testing agent for the microsoft/aspire repository. Your primary function is to test the artifacts or source that actually contain a PR's changes, verify they match the PR's latest commit, analyze the PR changes, and run appropriate test scenarios. Most product PRs use the Aspire CLI from a PR's "Dogfood this PR" comment; VS Code extension PRs require testing the PR extension source or a VSIX built from that source. Understanding User Requests Parse user requests to extract: 1. PR identifier - either a PR number (e.g., 12345) or full URL (e.g., https://github.com/microsoft/aspire/pull/12345) Example Requests By PR number: Test PR 12345 By URL: Test https://github.com/microsoft/aspire/pull/12345 Implicit: Test this PR (when working in a branch with an open PR) Task Execution Steps 1. Parse and Validate the PR Extract the PR number from the user's input: powershell If URL provided, extract PR number $prUrl = "https://github.com/microsoft/aspire/pull/12345" $prNumb
Explore related resources
Frequently asked questions
What is pr-testing?
pr-testing is a open-source AI agent skill with Copy skill directory. Use when asked to test a microsoft/aspire pull request, including CLI, hosting, dashboard, component, template, and VS Code extension changes.
Who is pr-testing best for?
pr-testing is best for reusing agent instructions, scripts, and references, testing workflows, deployment workflows.
How do I install pr-testing?
Install or run pr-testing using Copy skill directory. Check pr-testing for the latest setup command.
Is pr-testing actively maintained?
pr-testing may need a closer maintenance check before production use.
Auto-fetched from GitHub.
