GitHub, Git & DevOps · IN-DEPTH PROFILE

Pr Screenshots Skill

Matched before-and-after visual evidence for pull requests, including upload and sizing guidance.

View listed source ↗Installation guide ↓
Best for

Teams reviewing visible UI or output changes

What you get

Capture matched states + Annotate the review

Main limitation

GitHub has no clean public API for PR-description image upload in this workflow.

First risk

Sensitive data in shared screenshots. Screenshots may expose customer data, tokens, internal URLs, or account details. Use fixtures, crop carefully, redact before upload, and verify repository visibility.

EVIDENCE FRESHNESS

Three checks, kept separate

A recent source check is not a runtime test or security audit.

Upstream sourceChecked 2026-09-24

Pinned revision · 1f564408

Open pinned commit ↗
SkillSignal profileEditorial metadata

Updated 2026-09-24

Runtime & securityNot independently verified

Source review does not certify behavior or safety.

IN PLAIN ENGLISH

What it does—and when it fits

PR Screenshots is a GitHub Awesome Copilot guide for putting matched before-and-after visual evidence directly into pull-request descriptions. It covers consistent capture, concise annotation, image sizing, Azure DevOps attachments, and the current GitHub upload workaround.

This is aimed at Teams reviewing visible UI or output changes. Compare the examples below with your task, then review the limitations, permissions, and risks before installing.

What you get
  • Capture matched statesUse the same viewport and crop before and after a visual change.
  • Annotate the reviewAdd a short sentence explaining what the reviewer should notice.
  • Publish PR evidenceUpload through the supported platform path and embed visible images.
What makes it different
  • Lets reviewers understand visual changes without checking out the branch.
  • Matched viewport and crop make comparisons more credible.
Community signalNo attributed third-party rating yet

No verified review text is in the current dataset. Use the linked source for the latest discussion.

Read the source note ↗

INSTALL BY AGENT

Choose your Agent

Paths come from official Agent docs or the universal installer behind skills.sh. Compatibility still follows this Skill's record.

Native

This Skill's current record explicitly names this Agent. Still inspect scripts, permissions, and external dependencies first.

Project install (recommended)
npx skills add github/awesome-copilot --skill pr-screenshots --agent github-copilot
Personal install
npx skills add github/awesome-copilot --skill pr-screenshots --agent github-copilot -g

Project install stays with this repository for team sharing. Personal install adds -g and works across repositories.

View install paths
Project path.agents/skills/pr-screenshots/
Personal path~/.copilot/skills/pr-screenshots/
Official agent docs

Copilot also accepts .github/skills and .claude/skills at project scope. Preview untrusted Skills before enabling scripts.

View path evidence ↗

TYPICAL WORKFLOW

A practical workflow

01

Capture matched states

Use the same viewport and crop before and after a visual change.

02

Annotate the review

Add a short sentence explaining what the reviewer should notice.

03

Publish PR evidence

Upload through the supported platform path and embed visible images.

THE TRADEOFFS

Advantages and tradeoffs

Notable strengths

  1. Lets reviewers understand visual changes without checking out the branch.
  2. Matched viewport and crop make comparisons more credible.

Limitations

  1. GitHub has no clean public API for PR-description image upload in this workflow.
  2. Screenshots show selected states and cannot prove interaction, responsiveness, or accessibility.

COMPARE THE TRADEOFF

Consider these close alternatives

These are deterministic nearby candidates, not paid placements or a universal ranking. Open the full profile before choosing.

01

Same job family · native to GitHub Copilot

commit-message-storyteller

Narrative Conventional Commit messages that explain intent, impact, and logical change boundaries.
Tradeoff to check
A diff often cannot reveal the true motivation, user impact, or issue context.
First risk
Incorrect intent inferred from code · Medium
Source state
Pinned · 1f564408
Open commit-message-storyteller profile ↗
02

Same job family · native to GitHub Copilot

containerize-aspnet-framework

Create Windows container files for ASP.NET Framework projects.
Tradeoff to check
Detailed package files are not fully catalogued.
First risk
Review before install · Medium
Source state
Pinned · 1f564408
Open containerize-aspnet-framework profile ↗
03

Same job family · native to GitHub Copilot

create-github-issues-feature-from-implementation-plan

Split implementation-plan phases into trackable GitHub issues.
Tradeoff to check
Detailed package files are not fully catalogued.
First risk
Review before install · Medium
Source state
Pinned · 1f564408
Open create-github-issues-feature-from-implementation-plan profile ↗
Compare more in the directory →

BEST FIT

Who it is for

→

Teams reviewing visible UI or output changes

→

Authors who need durable visual evidence in pull requests

BEFORE YOU USE IT

Risks to review before use

High

Sensitive data in shared screenshots

Screenshots may expose customer data, tokens, internal URLs, or account details. Use fixtures, crop carefully, redact before upload, and verify repository visibility.

SECURITY

What the permission profile means

  • Use non-production data and inspect every image at native resolution.
  • Do not commit screenshots to the product branch solely for hosting.

Not a security certification. External ratings are attributed references. SkillSignal has not independently executed or security-reviewed this Skill.

COMMON QUESTIONS

Pr Screenshots Skill FAQ

What is the Pr Screenshots Skill?

Matched before-and-after visual evidence for pull requests, including upload and sizing guidance. PR Screenshots is a GitHub Awesome Copilot guide for putting matched before-and-after visual evidence directly into pull-request descriptions. It covers consistent capture, concise annotation, image sizing, Azure DevOps attachments, and the current GitHub upload workaround.

How do I install the Pr Screenshots Skill?

Open and review the listed source, choose the project or personal path for your Agent, then verify the first run in a controlled project. Open the pinned commit and read the current SKILL.md.

Is the Pr Screenshots Skill safe to use?

SkillSignal checked the source on 2026-09-24, but that is not a runtime test or security certification. Review the “Sensitive data in shared screenshots” risk first and begin with the least access required.

INSIDE THE PACKAGE

Indexed files

SKILL.mdUpstream package contentSource-linked

TAGS

pull-requestsscreenshotsvisual-evidence

Original SkillSignal editorial profile grounded in GitHub Awesome Copilot commit d7e4ad98, checked 2026-09-23; not independently executed or security-certified.