Create temporary PR-specific screenshots and short GIF demos without committing scene code to the product branch. Use automatically when a visually meaningful frontend change materially benefits from visual review, and when the user requests PR media. Do not use for backend-only, non-visual, or already-sufficiently-proven changes.
Scanned 9/20/2026
Install to Claude Code
npx -y skills add ayunis-core/ayunis-core --skill pr-media --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Pr Media?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/ayunis-core-pr-media)More formats (shields.io, HTML) on the badges page.
---
name: pr-media
description: Create temporary PR-specific screenshots and short GIF demos without committing scene code to the product branch. Use automatically when a visually meaningful frontend change materially benefits from visual review, and when the user requests PR media. Do not use for backend-only, non-visual, or already-sufficiently-proven changes.
---
# PR Media
PR media scenes are temporary review aids. Never commit scene definitions to the product PR. Store them on the disposable `pr-media/pr-<number>` branch; the App Integration workflow deletes that branch when the PR closes.
Use the Proportional Workflow to decide whether PR media adds meaningful review evidence. When it does, capture only the affected viewports and states: use desktop and mobile when responsive behavior is relevant, and add a short GIF when motion or interaction cannot be judged from a static screenshot. Do not create media as ceremony for changes the diff and focused tests already make clear.
## Workflow
1. Ensure the product PR exists and the current branch is its head:
```bash
gh pr view --json number,url,headRefName
```
2. Decide the smallest scene set that shows the changed UI. Do not auto-detect routes or capture unrelated pages. Write a temporary scene file outside the repo, e.g. `/tmp/pr-media-scenes.ts`.
3. Upload it to the media branch:
```bash
scripts/update-scenes.sh --pr <number> /tmp/pr-media-scenes.ts
```
4. Re-run or wait for the App Integration workflow. It will fetch `.pr-media/scenes.ts` from `pr-media/pr-<number>`, capture media with read-only permissions, then publish generated PNG/GIF files back to the same branch and upsert the sticky PR comment.
## Scene file shape
```ts
import type { PrMediaScene } from './types';
export default [
{
name: 'admin-users-invite',
path: '/admin-settings/users',
viewports: ['desktop', 'mobile'],
waitFor: async ({ page }) => page.getByTestId('settings-sidebar'),
demos: [
{
name: 'invite-dialog',
action: async ({ page }) => {
await page.getByRole('button').last().click();
},
},
],
},
] satisfies PrMediaScene[];
```
Guidelines:
- Keep scene and demo names kebab-case (`^[a-z0-9]+(?:-[a-z0-9]+)*$`); CI rejects unsafe names before publishing. Output is `scene-name--viewport.png` and `scene-name--demo-name--viewport.gif`.
- Use `getByTestId` / `getByRole`; avoid text selectors where possible because the UI is localized.
- Prefer short, deterministic interactions. No `waitForTimeout`; wait on locators or assertions.
- Include only the scenes needed to demonstrate the changed UI; do not capture unrelated pages or states.
## Verify
```bash
gh api repos/$GITHUB_REPOSITORY/git/ref/heads/pr-media/pr-<number>
gh pr checks <number> --watch --interval 30
```
Confirm the sticky `<!-- pr-screenshots -->` comment contains the expected PNG/GIF names.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!