Skip to content
Skill

PR screenshots

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

Install
Scripts
None
Platforms
Claude Code, Codex, Cursor
GitHub stars
41.3K
Last commit
1 day ago
License
MIT
Listing updated
today

When your agent uses it

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.

From the skill's SKILL.md. Your agent reads this description to decide when to load the skill.

What it can access

From a static check of its 1 file (5 KB) on GitHub on 17 November 2026. Nothing was run. Read the files before you install a skill: it can tell your agent to run anything its tools allow.

Install

Copy the skill folder to ~/.claude/skills/pr-screenshots to use it in all your projects:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/github/awesome-copilot.git "$tmp" &&
mkdir -p ~/.claude/skills &&
rm -rf ~/.claude/skills/pr-screenshots &&
cp -R "$tmp/skills/pr-screenshots" ~/.claude/skills/pr-screenshots &&
rm -rf "$tmp"

For one project only, put the folder in .claude/skills/pr-screenshots inside it instead.

Claude Code docs on skills

Copy the skill folder to ~/.agents/skills/pr-screenshots to use it in every repository:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/github/awesome-copilot.git "$tmp" &&
mkdir -p ~/.agents/skills &&
rm -rf ~/.agents/skills/pr-screenshots &&
cp -R "$tmp/skills/pr-screenshots" ~/.agents/skills/pr-screenshots &&
rm -rf "$tmp"

For one repository only, put the folder in .agents/skills/pr-screenshots inside it instead.

Codex docs on skills

Copy the skill folder to ~/.cursor/skills/pr-screenshots to use it in every project:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/github/awesome-copilot.git "$tmp" &&
mkdir -p ~/.cursor/skills &&
rm -rf ~/.cursor/skills/pr-screenshots &&
cp -R "$tmp/skills/pr-screenshots" ~/.cursor/skills/pr-screenshots &&
rm -rf "$tmp"

For one project only, put the folder in .cursor/skills/pr-screenshots inside it instead.

Cursor docs on skills

Run in a terminal (add --scope workspace to install it for the current workspace only):

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

Or copy the folder to ~/.gemini/skills/pr-screenshots yourself.

Gemini CLI docs on skills

For GitHub Copilot in VS Code, copy the skill folder to ~/.copilot/skills/pr-screenshots:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/github/awesome-copilot.git "$tmp" &&
mkdir -p ~/.copilot/skills &&
rm -rf ~/.copilot/skills/pr-screenshots &&
cp -R "$tmp/skills/pr-screenshots" ~/.copilot/skills/pr-screenshots &&
rm -rf "$tmp"

For one project only, put the folder in .github/skills/pr-screenshots inside it instead.

VS Code docs on skills

Get the folder:

git clone --depth 1 https://github.com/github/awesome-copilot.git

Then copy awesome-copilot/skills/pr-screenshots into your agent's skills folder as pr-screenshots. Agents that support SKILL.md read one folder per skill.

The SKILL.md format

PR screenshots FAQ

How do I install PR screenshots in Claude Code?

Copy the skill folder from GitHub to ~/.claude/skills/pr-screenshots to use it in all your projects, or to .claude/skills/pr-screenshots in one project.

Does PR screenshots run scripts?

No. It is instructions only, with no scripts. This comes from a static check of the files on GitHub; nothing was run. Read the files before you install it.

Which AI agents can use PR screenshots?

Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose. Each reads skills in the SKILL.md format from its own folder; the install steps on this page list them.

What are the best alternatives to PR screenshots?

The closest alternatives to PR screenshots are Rea changelog update, Code review, Gem devops guidelines, Github actions efficiency and Github actions runtime upgrade conventions.

More from github/awesome-copilot

  1. Design or review infrastructure, deployment, CI/CD, Docker, Kubernetes, health checks, rollback, feature flags, production readiness, and mo

    • Open source
    • 41.3K GitHub stars
    • Cloud and infrastructure
  2. Stop coding agents from shipping generic UI

    • Open source
    • 41.3K GitHub stars
  3. Cross-references C# Web API controllers/DTOs against their TypeScript/JavaScript consumers (React, Angular, Vue, Svelte, Node.js, or hand-wr

    • Open source
    • 41.3K GitHub stars
  4. Serves as a reviewer of the codebase with instructions on looking for Apple App Store optimizations or rejection reasons.

    • Open source
    • 41.3K GitHub stars
  5. Triage and resolve Arch Linux issues with pacman, systemd, and rolling-release best practices.

    • Open source
    • 41.3K GitHub stars

Alternatives to PR screenshots

  1. Prepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Ple

    • Open source
    • 465K GitHub stars
    • Developer tools
  2. Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's docu

    • Open source
    • 326K GitHub stars
    • Developer tools
  3. Design or review infrastructure, deployment, CI/CD, Docker, Kubernetes, health checks, rollback, feature flags, production readiness, and mo

    • Open source
    • 41.3K GitHub stars
    • Cloud and infrastructure
  4. Audit GitHub Actions workflow efficiency and recommend fixes to reduce CI minutes and costs.

    • Open source
    • 41.3K GitHub stars
    • Developer tools
  5. Upgrade GitHub Actions to supported runtimes by selecting safe action versions, preserving workflow behavior, and validating post-upgrade ex

    • Open source
    • 41.3K GitHub stars
    • Developer tools
  6. Perform an AWS Well-Architected Framework review of the current workload IaC and architecture, generating findings and GitHub issues for imp

    • Open source
    • 41.3K GitHub stars
    • Cloud and infrastructure