GitHub, Git & DevOps · IN-DEPTH PROFILE

pr-screenshots

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-08-20

Pinned revision · 318066d2

Open pinned commit ↗
SkillSignal profileEditorial metadata

Updated 2026-08-20

Runtime & securityNot independently verified

Source review does not certify behavior or safety.

30-SECOND BRIEF

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.

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 scope.agents/skills/pr-screenshots/
Personal scope~/.copilot/skills/pr-screenshots/

Use project scope for team sharing and personal scope across repositories. The installer defaults to project scope; add -g for personal scope.

Install command (project scope)npx skills add github/awesome-copilot --skill pr-screenshots --agent github-copilot
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 · 318066d2
Open profile ↗
02

Same job family

supply-chain-risk-auditor

Measured dependency risk reports covering advisories, maintainers, abandonment, and install scripts.
Tradeoff to check
Does not fully parse yarn.lock, pnpm-lock.yaml, poetry.lock, or unsupported ecosystems.
First risk
Registry and repository metadata exposure · High
Source state
Pinned · 9b281335
Open profile ↗
03

Same job family

appinsights-instrumentation

AppInsights Instrumentation is a reference Skill for adding Azure Application Insights telemetry patterns and SDK configuration to supported web applications.
Tradeoff to check
It is guidance only; requests to add or change components must route to Azure Prepare.
First risk
Sensitive or excessive telemetry · High
Source state
Pinned · ea76537e
Open 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.

INSIDE THE PACKAGE

Indexed files

SKILL.mdUpstream package contentSource-linked

TAGS

pull-requestsscreenshotsvisual-evidence

Original SkillSignal editorial profile grounded in GitHub Awesome Copilot commit 318066d2, checked 2026-08-20; not independently executed or security-certified.