PR Media
SkillDev toolsCreate temporary PR-specific screenshots and short GIF demos without committing scene code to the product branch. Use when the user requests PR media or when a visually meaningful frontend change materially benefits from visual review. It is not automatic for every frontend diff.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the PR Media skill
What this skill tells your AI
The instructions your AI receives, as published by ayunis-core/ayunis-core in .claude/skills/pr-media/SKILL.md and read by ahel’s review.
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
-
Ensure the product PR exists and the current branch is its head:
gh pr view --json number,url,headRefName -
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. -
Upload it to the media branch:
scripts/update-scenes.sh --pr <number> /tmp/pr-media-scenes.ts -
Re-run or wait for the App Integration workflow. It will fetch
.pr-media/scenes.tsfrompr-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
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 isscene-name--viewport.pngandscene-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
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.
Signals
- GitHub stars
- 33
- Forks
- 3
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
pr-media- Source
- github.com/ayunis-core/ayunis-core