Skip to content
cccskills
FreePublished on GitHub

pr-media

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.

The English summary is being prepared. Showing the original description.

ayunis-core/ayunis-core34 stars(GitHub 34 + cccskills 0)
Works withGitHub

Run score Not tested

See how to install

Files included (1)

  • SKILL.md2.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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:

    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:

    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

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

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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Query Ayunis deployed-environment telemetry in AppSignal — incidents, occurrence counts and error traces via the `appsignal-cli` binary; structured log attributes (user.id, org.id, nestjs.context, custom metadata) via the v2 logs API. Use when investigating a production/staging incident or log data — NOT for local dev logs (see backend-debugging).

The English summary is being prepared. Showing the original description.

ayunis-core/ayunis-core34Updated Oct 26, 2026

Ayunis Core backend specifics — module boundaries, key files, and project conventions. Complements the nestjs-hexagonal-backend skill.

The English summary is being prepared. Showing the original description.

ayunis-core/ayunis-core34Updated Oct 26, 2026

Frontend development in ayunis-core. Use when creating, modifying, or debugging frontend code (React, Feature-Sliced Design, API client).

The English summary is being prepared. Showing the original description.

ayunis-core/ayunis-core34Updated Oct 26, 2026

Debug backend runtime errors (500s, crashes, unexpected behavior). Use when something is broken at runtime — not for writing new code.

The English summary is being prepared. Showing the original description.

ayunis-core/ayunis-core34Updated Oct 26, 2026

Shared test fixtures for backend specs — port mock factories, domain builders, and shared IDs in a per-module testing/ folder. Use when a module's *.use-case.spec.ts files repeat the same mock-repository literal, inline entity construction, or hardcoded UUIDs across files.

The English summary is being prepared. Showing the original description.

ayunis-core/ayunis-core34Updated Oct 26, 2026

Analyze Cursor Bugbot PR comments through a root-cause lens: is the finding valid, and is the suggested fix the real fix or a bandaid over a deeper problem? Use when the user asks to check, assess, or triage bugbot comments.

The English summary is being prepared. Showing the original description.

ayunis-core/ayunis-core34Updated Oct 26, 2026

See all skills by ayunis-core

Report a problem with this skill