pr-screenshots
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.
Profile →npx skills add github/awesome-copilot --skill pr-screenshots --agent copilot
Same command for any agent — swap --agent for claude-code, codex, cursor.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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:  **After** — brief description of the fix:  ``` 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:  **After** — borders overlap cleanly, hover tint added:  ## Chart tooltip **Before** —
- When to Use This Skill
- PR Description Pattern
- Multiple changes
- Image Sizing
- Uploading Images
- Azure DevOps
- GitHub
- Guidelines
- Limitations
What does the pr-screenshots skill do?
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.
How do I install it?
Run `npx skills add github/awesome-copilot --skill pr-screenshots --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.