---
title: "visual-pr"
description: "Capture, annotate, and embed screenshots and animated GIF demos in pull request descriptions. Includes Playwright-based UI capture, PIL image annotations, PR embedding workflows for GitHub and Azure DevOps, and screen re"
canonical: https://agentpluginsdirectory.com/plugins/visual-pr
last-updated: 2026-09-12
---

# visual-pr
Capture, annotate, and embed screenshots and animated GIF demos in pull request descriptions. Includes Playwright-based UI capture, PIL image annotations, PR embedding workflows for GitHub and Azure DevOps, and screen recording with variable timing.
- Slug: visual-pr
- Publisher: Awesome Copilot Community
- Repository: https://github.com/rakthainet-DKH/FormTH-copilot
- Manifest: plugins/visual-pr/plugin.json
- Version: 1.0.0
- License: MIT
- Category (editorial): other
- Skills: 0
- MCP servers: 0
- Stars: 0
- Repository created: 2026-09-11
- Repository last pushed: 2026-09-11
- Publisher type: User
- Listing: https://agentpluginsdirectory.com/plugins/visual-pr
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What visual-pr does, in the publisher's words

When you change how something looks, a layout, a chart, a form, the PR description should show the change. Not describe it in words. Show it. A before/after screenshot tells your reviewer exactly what happened, and they don't have to check out the branch to see it.

This plugin teaches Copilot to capture screenshots of your web app (or any UI), annotate them with callouts, and embed them in the PR description. Once you get used to having up-to-date screenshots on every visual change, going back to text-only PRs feels like reviewing code with your eyes closed.

It is 2009. You just added the feature to show labels on issues. You better include screenshots because this is huge.

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/rakthainet-DKH/FormTH-copilot/HEAD/plugins/visual-pr/README.md