github-image-upload

Use when a GitHub PR, issue, or comment needs screenshots, recordings, test results, or other visual or text evidence.

By jssblck · 781 installs

npx skills add jssblck/agents --skill github-image-upload

Source repository · Upstream listing

Attach proof on GitHub Use attach on gh pr create , edit , or comment , or the corresponding gh issue command. Publication must be authorized by the task. Inline text evidence in a language tagged fence; attach accepts images and videos. Check gh version and authentication if they are not already established. If the installed CLI lacks attach , continue preparing the proof and report the version needed. A request to upload proof does not authorize upgrading the CLI. Attach to the intended destination Identify the repository, PR or issue, and whether the destination is its body or a particular comment. Preserve existing content. Do not commit proof files. Write a multiline body to a file and pass body file . An image reference whose destination matches the attachment path is replaced with the uploaded URL: For an appended attachment, attach '/abs/path/error.png Error state' supplies alt text. Repeat the flag for multiple files. Videos render as players when their image reference has empty alt text and occupies its own paragraph. Verify and recover Read the specific body or comment that the command created or changed. Verify each requested file has its corresponding uploaded URL in that destination, using the command result and the attachment's surrounding text. An attachment elsewhere in the thread does not prove this upload succeeded. A nonzero exit can still leave a created PR or comment and some uploaded files. Inspect that result before retrying. Preserve successful uploads, correct a recoverable error, and edit the existing destination with only the missing files. Never replay a create or comment command blindly. If the result is uncertain or access prevents repair, report what succeeded and what remains. For a private repository, verify with the signed in account; an anonymous 403 or 404 does not establish failure. Text only proof needs its intended fenced content, not an attachment URL.