run-examples

Map PR changes to relevant examples and await approval before running.

1.2k|259|Updated Apr 17, 2025
One-click install
npx skills add https://github.com/symfony/ai --skill run-examples-symfony
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-examples
Source: https://github.com/symfony/ai/tree/main/.claude/skills/run-examples
Command: npx skills add https://github.com/symfony/ai --skill run-examples-symfony

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintainers select and execute a focused set of examples for a given PR by mapping changed files in the repository to the relevant entries under examples/ and presenting a candidate subset for verification before any execution.

Core Features & Use Cases

  • Maps code changes to the smallest, most relevant set of examples to exercise the modified behaviour.
  • Proposes candidates with reasons and skip notes, and waits for explicit approval before running.
  • Handles missing environment keys and optional Docker requirements by surfacing gaps without auto-running anything.

Quick Start

Propose the candidate examples and await approval before executing any run.

Frequently Asked Questions about run-examples

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

FAQPage Schema
How do I run specific examples to validate PR changes without testing the entire codebase?

To validate PR changes, this automation tool maps modified files to the minimal relevant examples in the examples/ directory and presents a candidate subset for review. It waits for explicit approval before running any selected examples.

How does mapping code changes to examples work for pull request validation?

Mapping code changes works by analyzing the modified files in a pull request and matching them to the smallest set of examples that exercise the altered behavior. It presents these candidates with reasons and skip notes before execution.

Do I need Docker to run PR-relevant examples for code review?

Docker is an optional requirement for running PR-relevant examples. The tool surfaces missing Docker services and environment keys to the maintainer prior to execution rather than auto-running and failing.

Can I review and approve which examples run before they are executed?

Yes, you can review and approve examples before execution. The runner proposes a candidate list with reasons and skip notes, and strictly awaits explicit approval before executing any run.

What happens if my environment is missing required keys for example validation?

If environment keys are missing, the tool flags these gaps to allow the maintainer to address them prior to execution. It surfaces missing requirements without auto-running anything to prevent execution failures.

What is the best way to automate focused example execution for a pull request?

The best way to automate focused example execution is mapping changed files to the minimal relevant examples and presenting them for approval. This ensures only the necessary examples run, avoiding full suite execution.