testing-pr-changes

Verify agent-created pull requests with local tests and Playwright screenshots.

1|Updated Feb 7, 2016

Search Tags:#testing #ci/cd #pull request #verification #agent #playwright

Ready to run

npx skills add https://github.com/ynotradio/site --skill testing-pr-changes

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: testing-pr-changes
Source: https://github.com/ynotradio/site/tree/main/.claude/skills/testing-pr-changes
Command: npx skills add https://github.com/ynotradio/site --skill testing-pr-changes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that changes made by AI agents are thoroughly tested and verified before being submitted as pull requests, preventing broken builds and ensuring functionality.

Core Features & Use Cases

Comprehensive Testing: Guides agents through critical local checks including linting, unit tests, and end-to-end tests.
Visual Verification: Mandates the use of Playwright for capturing screenshots to prove functionality.
Performance Monitoring: Provides clear thresholds for build and startup times, flagging performance regressions.
Use Case: An agent modifies a website's footer. This skill ensures the agent runs all tests, captures a screenshot of the updated footer on the live site, and checks that build times haven't significantly increased.

Quick Start

Use the testing-pr-changes skill to verify all local tests pass and capture a screenshot of the updated UI.

Frequently Asked Questions about testing-pr-changes

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

FAQPage Schema

How do I verify AI agent pull requests before merging?▼

To verify AI agent pull requests, you need a comprehensive workflow that runs local linting, unit tests, and end-to-end checks. This ensures automated quality assurance for AI-generated code changes by validating functionality and preventing broken builds before submission.

How do I use Playwright to capture screenshots for pull request verification?▼

Using Playwright to capture screenshots for pull request verification provides visual proof of functionality. It mandates capturing screenshots of updated UI elements on a live site to confirm that agent-created code changes render correctly and function as intended.

What is included in an automated checklist for testing agent-created code changes?▼

An automated checklist for testing agent-created code changes includes local linting, unit tests, end-to-end verification using Playwright, and performance baseline checks. It also provides fallback strategies for reporting blockers when automated quality assurance cannot complete.

How do I check performance baselines for AI-generated pull requests?▼

Checking performance baselines for AI-generated pull requests involves monitoring build and startup times against clear thresholds. This flags performance regressions early, ensuring that agent modifications do not significantly degrade application speed or build efficiency.

What should I do if local testing fails during agent PR verification?▼

If local testing fails during agent PR verification, you should utilize fallback strategies for reporting blockers. This involves documenting the specific test failures or performance regressions encountered to prevent broken builds from being submitted as pull requests.