github-pr-proof-assets

Upload screenshots and videos to GitHub and post them as PR or issue comments.

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/celeroncoder/skills --skill github-pr-proof-assets-celeroncoder
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-pr-proof-assets
Source: https://github.com/celeroncoder/skills/tree/main/github-pr-proof-assets
Command: npx skills add https://github.com/celeroncoder/skills --skill github-pr-proof-assets-celeroncoder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Attaching screenshots or videos to GitHub pull requests and issues normally requires manual drag-and-drop in the web UI. This Skill automates uploading proof assets through GitHub's user-attachments endpoint and posting the returned URLs as comments with the gh CLI. ## Core Features & Use Cases - Asset Upload: Uploads PNG, JPEG, WebP, MP4, and WebM files to GitHub's user-attachments endpoint using the authenticated gh token. - Video Validation and Transcoding: Inspects video format, duration, and dimensions with ffprobe and transcodes incompatible video to broadly playable MP4 with ffmpeg. - Comment Posting and Verification: Builds Markdown with image alt text or bare video URLs, posts it via gh pr/issue comment, and verifies the published comment contains every attachment URL. - Use Case: After fixing a UI bug, upload before/after screenshots and a QA reproduction video to the pull request as proof, then confirm the comment published correctly. ## Quick Start Upload these screenshots and the QA video to pull request 42 and post them as a comment with descriptive alt text.

Frequently Asked Questions about github-pr-proof-assets

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

FAQPage Schema
How do I attach screenshots to a GitHub pull request from the command line?▼

Upload the image file to GitHub's user-attachments endpoint with curl using your gh auth token, then post the returned URL as Markdown image syntax in a PR comment via gh pr comment. The endpoint requires the numeric repository ID and a supported MIME type.

How to upload a video to a GitHub issue comment?▼

Validate the video with ffprobe, transcode it to MP4 with ffmpeg if needed, then POST it to uploads.github.com/user-attachments/assets with the repository ID. Place the returned URL on its own bare line in the comment body so GitHub renders the video player.

What file types does GitHub user-attachments upload support?▼

This workflow supports image/png, image/jpeg, image/webp, video/mp4, and video/webm. Verify the actual MIME type with file --mime-type before uploading, since a mismatch between the file content and declared type causes a 422 error.

Why does GitHub asset upload return 404 Not Found?▼

A 404 usually means the numeric repository ID does not match the intended OWNER/REPO, or the authenticated account lacks push access to that repository. Verify the ID with gh api repos/OWNER/REPO and check permissions with gh auth status.

Why does GitHub asset upload fail with 422 Unprocessable Entity?▼

A 422 error means the MIME type is unsupported or does not match the actual file content. Re-run file --mime-type to confirm the real type, use one of the supported image or video formats, and transcode incompatible video to MP4 with ffmpeg.