gh-comment-attach-files

# GitHub Comment Attach Files ## Read Acknowledgement - After reading this skill, say: `🐙 私は gh-comment-attach-files を読みました。` ## When To Use Use this skill when you need GitHub to host local files and give back anonymized attachment URLs, but you do not want the agent to submit the issue or pull request comment itself. Typical cases: - Upload PNG, JPG, PDF, Markdown, or other GitHub-supported attachments to a PR or issue comment box. - Replace broken local image URLs in a draft report with GitHub-hosted URLs. - Work against either `github.com` or GitHub Enterprise Server. Do not use this skill when the task is to actually post, edit, or rewrite a comment. This skill stops after URL acquisition. ## Prerequisites - `npx @playwright/cli` must be available. - If you use `--repo ... --issue ...` or `--repo ... --pr ...`, `gh` must be installed and authenticated. - If GitHub redirects to login or SSO, finish authentication in the opened browser window while the script is polling for the comment composer. ## Workflow 1. Resolve the target page from either a direct URL or `gh` metadata. 2. Stage the requested files under `./.playwright-cli/gh-comment-attach-files/...`. 3. Open the issue or pull request page with a persistent Playwright CLI browser profile. 4. Find the main comment composer and attach files one by one. 5. Read the inserted Markdown and return JSON with `target_url`, `source_path`, `staged_name`, and `attachment_url`. 6. Close the browser unless `--leave-op...