gh-pr-with-screenshots

Create or update GitHub PRs with embedded UI screenshots from the current branch.

1|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/harley/useful-skills --skill gh-pr-with-screenshots
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-pr-with-screenshots
Source: https://github.com/harley/useful-skills/tree/main/gh-pr-with-screenshots
Command: npx skills add https://github.com/harley/useful-skills --skill gh-pr-with-screenshots

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates creating or updating a GitHub PR from the current branch, and attaches UI screenshots to the PR description for quick visual verification.

Core Features & Use Cases

  • PR workflow automation: Detects the current branch, pushes it to origin, and ensures a PR exists against main.
  • Screenshot integration: Captures UI screenshots with browser-tools and stores them under a screenshots/ folder.
  • PR body enrichment: Updates the PR description with image links using blob URLs for reliable embedding.
  • Use Case: When delivering a UI feature, run this to generate a PR that includes visual references for reviewers.

Quick Start

Push your feature branch and run the workflow to create or update the PR with embedded UI screenshots.

Frequently Asked Questions about gh-pr-with-screenshots

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add UI screenshots to a GitHub pull request automatically?

To add UI screenshots to a GitHub pull request, this workflow pushes your current branch, discovers or creates a PR against main, captures UI screenshots via browser tooling, and updates the PR body with embedded blob URLs.

What's the best way to automate pull request creation with visual verification?

Automating pull request creation with visual verification is best handled by a workflow that detects your current branch, pushes to origin, creates the PR if missing, and attaches UI screenshots to the description for reviewer reference.

How does screenshot integration work when creating a PR from a feature branch?

Screenshot integration works by capturing UI screenshots with browser-tools, storing them under a screenshots/ folder, and updating the PR description with image links using blob URLs for reliable embedding.

Do I need browser-automation tooling to attach screenshots to a PR?

Yes, browser-automation tooling is required to capture UI screenshots during the PR workflow. The skill uses browser tooling to capture visual references and stores them in a screenshots/ folder before updating the PR body.

Can I update an existing GitHub PR with new UI screenshots from my branch?

Yes, you can update an existing GitHub PR with new UI screenshots. The workflow discovers existing PRs against main, pushes your current branch, captures fresh UI screenshots, and enriches the PR body with updated blob URLs.

When should I use an automated PR workflow with embedded screenshots?

You should use an automated PR workflow with embedded screenshots during feature development when visual verification of UI changes is desired and PRs require accompanying visual references for reviewers.