Official agent skill

PR Screenshots

Embed before/after screenshots and annotated images in pull request descriptions.

OfficialMITAuto-check passedDevelopment

Install PR Screenshots

skills CLI

$ npx skills add github/awesome-copilot --skill pr-screenshots -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install github/awesome-copilot pr-screenshots --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/pr-screenshots .claude/skills/pr-screenshots && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "pr-screenshots" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/pr-screenshots into .claude/skills/pr-screenshots/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-screenshots", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/github/awesome-copilot/tree/main/skills/pr-screenshots

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add github/awesome-copilot --skill pr-screenshots -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install github/awesome-copilot pr-screenshots --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/pr-screenshots .agents/skills/pr-screenshots && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "pr-screenshots" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/pr-screenshots into .agents/skills/pr-screenshots/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-screenshots", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add github/awesome-copilot --skill pr-screenshots -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install github/awesome-copilot pr-screenshots --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/pr-screenshots .cursor/skills/pr-screenshots && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "pr-screenshots" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/pr-screenshots into .cursor/skills/pr-screenshots/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-screenshots", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/github/awesome-copilot.git --path skills/pr-screenshots

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add github/awesome-copilot --skill pr-screenshots -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install github/awesome-copilot pr-screenshots --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/pr-screenshots .gemini/skills/pr-screenshots && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "pr-screenshots" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/pr-screenshots into .gemini/skills/pr-screenshots/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-screenshots", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install github/awesome-copilot pr-screenshots

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add github/awesome-copilot --skill pr-screenshots -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/pr-screenshots .github/skills/pr-screenshots && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "pr-screenshots" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/pr-screenshots into .github/skills/pr-screenshots/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-screenshots", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add github/awesome-copilot --skill pr-screenshots -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install github/awesome-copilot pr-screenshots --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/pr-screenshots .opencode/skills/pr-screenshots && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "pr-screenshots" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/pr-screenshots into .opencode/skills/pr-screenshots/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-screenshots", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: pr-screenshots
GitHub stars: 40k
Token cost: ~1.2k tokens
SKILL.md length: 423 words
Files: 1
Skills in repo: 417
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Embed before/after screenshots and annotated images in pull request descriptions.

Works in 5 steps: Capture before state BEFORE making… → Keep descriptions brief — a sentence or… → Prefer visible images over collapsed… → …
Tasks that involve Pull requests
SKILL.md covers When to Use This Skill, PR Description Pattern, Image Sizing and Uploading Images, plus 2 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

PR Screenshots is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. Embed before/after screenshots and annotated images in pull request descriptions. Covers PR description patterns, image upload for Azure DevOps and GitHub, and sizing best practices.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Pull requests. It works with GitHub and Azure DevOps. The repository describes itself as: Community-contributed instructions, agents, skills, and configurations to help you make the most of GitHub Copilot. The licence is MIT.

When your agent uses it

Tasks that involve Pull requests

Example prompts

“/pr-screenshots”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

Capture before state BEFORE making changes — it's easy to forget, and reconstructing the original state later is slow and error-prone
Keep descriptions brief — a sentence or two per image pointing out what changed is enough
Prefer visible images over collapsed sections — screenshots behind tags are easy to skip
Annotate when the change is subtle — use the image-annotations skill to add callouts when the difference isn't immediately obvious
Match viewport and crop between before/after pairs so the comparison is meaningful

What it can do on your machine

Read from SKILL.md and the folder at commit 727ff2e. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown, html and powershell).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

PR Screenshots loads about 1.2k tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 423 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~49
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from github/awesome-copilot at commit 727ff2e, republished under its MIT licence (© github). 423 words, ~1,220 tokens.

Download SKILL.mdSave it as .claude/skills/pr-screenshots/SKILL.md (or your agent's skills folder).

name: pr-screenshots
description: Embed before/after screenshots and annotated images in pull request descriptions. Covers PR description patterns, image upload for Azure DevOps and GitHub, and sizing best practices.

PR Screenshots

Embed before/after screenshots in pull request descriptions so reviewers can see the visual change without checking out the branch.

When to Use This Skill

Use this skill when a PR changes something visible:

Layout, styling, CSS
Charts, dashboards, data visualizations
UI components, forms, modals
Error messages, CLI output, log formatting

PR Description Pattern

Place screenshots directly in the PR description body. Avoid wrapping them in <details> collapse — reviewers are more likely to look at images they can see without clicking.

markdown

**Before** — brief description of the problem:

![before](url-to-before-image)

**After** — brief description of the fix:

![after](url-to-after-image)

Keep the text brief. A sentence or two per image describing what the reader should notice. Let the image carry most of the communication.

Multiple changes

For PRs with several visual changes, use separate before/after pairs with headings:

markdown

## Filter bar alignment

**Before** — 1px border clash between adjacent buttons:

![before-filters](url)

**After** — borders overlap cleanly, hover tint added:

![after-filters](url)

## Chart tooltip

**Before** — tooltip clipped at container edge:

![before-tooltip](url)

**After** — tooltip repositions to stay visible:

![after-tooltip](url)

Image Sizing

Take screenshots at native 1x resolution — don't resize with PIL (creates artifacts)
Control display size in HTML when images are too large:
html
```
<img src="url" width="600" alt="description">
```
Before/after pairs must use the same viewport width and crop — otherwise the comparison is meaningless

Uploading Images

Azure DevOps

Upload images as PR attachments via the REST API:

powershell

$token = az account get-access-token `
    --resource "499b84ac-1321-427f-aa17-267ca6975798" `
    --query accessToken -o tsv

$base = "https://{org}.visualstudio.com/{projectId}/_apis/git/repositories/{repoId}"
$url = "$base/pullRequests/{prId}/attachments/screenshot.png?api-version=7.1-preview.1"

# Use HttpClient — Invoke-RestMethod can corrupt binary data
$client = New-Object System.Net.Http.HttpClient
$client.DefaultRequestHeaders.Authorization = `
    New-Object System.Net.Http.Headers.AuthenticationHeaderValue("Bearer", $token)
$content = New-Object System.Net.Http.ByteArrayContent(
    , [System.IO.File]::ReadAllBytes("screenshot.png")
)
$content.Headers.ContentType = `
    [System.Net.Http.Headers.MediaTypeHeaderValue]::new("application/octet-stream")
$resp = $client.PostAsync($url, $content).Result

Reference in the PR description:

markdown

![description](https://{org}.visualstudio.com/{projectId}/_apis/git/repositories/{repoId}/pullRequests/{prId}/attachments/screenshot.png)

Azure DevOps gotchas:

Use {org}.visualstudio.com NOT dev.azure.com/{org} — AzDO's markdown renderer uses .visualstudio.com. The dev.azure.com format loads noticeably slower
Use POST not PUT (PUT returns 405)
API version must be 7.1-preview.1
Can't re-upload with the same filename — use a new name (e.g. screenshot-v2.png)
Use HttpClient not Invoke-RestMethod — IRM can corrupt binary data
Repo-relative paths don't work in PR descriptions — must use full URLs
Don't commit images to the branch just for PR screenshots

Show full SKILL.md (174 more words)Show less

GitHub

⚠️ Work in progress. GitHub's drag-and-drop image upload uses internal endpoints that require browser cookies. There's no clean public API for uploading images to PR descriptions yet.

Current workaround: Commit images to a pr-assets orphan branch and reference via blob URLs (github.com/{owner}/{repo}/blob/pr-assets/{file}?raw=true). It works but is clunky — contributions for a better approach are welcome.

Guidelines

Capture before state BEFORE making changes — it's easy to forget, and reconstructing the original state later is slow and error-prone
Keep descriptions brief — a sentence or two per image pointing out what changed is enough
Prefer visible images over collapsed sections — screenshots behind <details> tags are easy to skip
Annotate when the change is subtle — use the image-annotations skill to add callouts when the difference isn't immediately obvious
Match viewport and crop between before/after pairs so the comparison is meaningful

Limitations

GitHub image upload requires workarounds (no public API for PR description images)
Azure DevOps attachment filenames can't be reused — plan naming ahead
Very large images (>10MB) may not render inline on some platforms

Files

Just SKILL.md in skills/pr-screenshots of github/awesome-copilot.

Open the folder on GitHubat commit 727ff2e

Compare with similar skills

PR Screenshots next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

PR Screenshots compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
PR Screenshots this skillgithub/awesome-copilot	40k	—	~1.2k	Automated safety check: Pass	MIT	today
Respond To PR Commentsmicrosoft/PromptKit	110	—	~4.2k	Automated safety check: Pass	MIT	19 days ago
ONNX Runtime CI Managementmicrosoft/onnxruntime	22k	—	~4.1k	Automated safety check: Pass	MIT	today
PR Babysitteropeninterpreter/openinterpreter	69k	3 repos	~4.2k	Automated safety check: Pass	Apache-2.0	today
Check PRonyx-dot-app/onyx	32k	2 repos	~2.3k	Automated safety check: Pass	MIT	today
Contributor-First PR MergeHKUDS/OpenHarness	16k	1 repos	~847	Automated safety check: Pass	MIT	4 mo ago

Similar skills

Respond To PR Comments
microsoft/PromptKit
Official
Respond to pull request review comments on GitHub or Azure DevOps Services.
110 GitHub stars~4.2k tokensUpdated 19 days ago
DevelopmentAuto-check passed
ONNX Runtime CI Management
microsoft/onnxruntime
Official
Triggers, re-runs and unblocks the CI checks on an ONNX Runtime pull request, after diagnosing whether a failure is transient or needs a code change.
22k GitHub stars~4.1k tokensUpdated today
DevOps & CloudAuto-check passed
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
69k GitHub starsUsed in 3 repos~4.2k tokens
DevelopmentAuto-check passed
Check PR
onyx-dot-app/onyx
Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.
32k GitHub starsUsed in 2 repos~2.3k tokens
DevelopmentAuto-check passed
Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
16k GitHub starsUsed in 1 repo~847 tokens
DevelopmentAuto-check passed
Create Pull Request
cline/cline
Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.
70k GitHub starsUsed in 1 repo~1.6k tokens
DevelopmentAuto-check passed

Questions about PR Screenshots

What does PR Screenshots do?

Embed before/after screenshots and annotated images in pull request descriptions. PR Screenshots is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. Embed before/after screenshots and annotated images in pull request descriptions.

When should I use PR Screenshots?

PR Screenshots fits situations like: tasks that involve Pull requests.

How do I install PR Screenshots in Claude Code?

Run `npx skills add github/awesome-copilot --skill pr-screenshots -a claude-code`. Or copy the skill folder (skills/pr-screenshots in github/awesome-copilot) into .claude/skills/pr-screenshots in your project. Claude Code loads it when a task matches its description.

How do I install PR Screenshots in Codex?

Run `npx skills add github/awesome-copilot --skill pr-screenshots -a codex`. Or copy the skill folder (skills/pr-screenshots in github/awesome-copilot) into .agents/skills/pr-screenshots in your project. Codex loads it when a task matches its description.

Can I use PR Screenshots in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add github/awesome-copilot --skill pr-screenshots -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pr-screenshots, .gemini/skills/pr-screenshots, .github/skills/pr-screenshots and .opencode/skills/pr-screenshots in your project.

What does PR Screenshots need to run?

SKILL.md names no scripts, command-line tools or credentials: PR Screenshots is instructions for the agent only.

Does PR Screenshots access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is PR Screenshots safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does PR Screenshots use?

PR Screenshots is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does PR Screenshots use?

About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to PR Screenshots?

Skills that share tags, products or a category with PR Screenshots: Respond To PR Comments (microsoft/PromptKit, 110 stars), ONNX Runtime CI Management (microsoft/onnxruntime, 22k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars) and Check PR (onyx-dot-app/onyx, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains PR Screenshots?

github (a GitHub organization, an official publisher) maintains it in github/awesome-copilot, which has 39,748 GitHub stars. The repository holds 417 skills in this directory. The repository was last updated on October 7, 2026.

Source: github/awesome-copilot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install PR Screenshots

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

PR Screenshots

When to Use This Skill

PR Description Pattern

Multiple changes

Image Sizing

Uploading Images

Azure DevOps

GitHub

Guidelines

Limitations

Files

Compare with similar skills

Similar skills

More from github/awesome-copilot

Related

Questions about PR Screenshots