file-github-issue

Files structured GitHub issues from screenshots and descriptions using the gh CLI.

Updated May 3, 2026
One-click install
npx skills add https://github.com/Claudfather/clauDNA --skill file-github-issue-claudfather
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: file-github-issue
Source: https://github.com/Claudfather/clauDNA/tree/main/skills/file-github-issue
Command: npx skills add https://github.com/Claudfather/clauDNA --skill file-github-issue-claudfather

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a screenshot of a bug into a well-structured GitHub issue normally requires manual screenshot hosting, body formatting, label selection, and duplicate checking. This Skill automates that entire filing workflow through the GitHub CLI. ## Core Features & Use Cases - Screenshot-to-issue pipeline: Extracts page URLs, error messages, and UI state from attached screenshots, then drafts a structured issue body with title, reproduction context, and related-issue links. - Image hosting via attachments repo: Commits screenshots to a user-configured public GitHub repo (set via CLAUDNA_ATTACHMENTS_REPO) and embeds raw URLs so images render inline in the issue. - Label pre-flight and duplicate search: Intersects proposed labels with labels that actually exist in the target repo, and searches for duplicate issues before filing. - Preview-and-confirm gate: Renders the full draft for user approval before anything is committed or filed. - Use Case: You spot a broken dashboard in your app, screenshot it, and say "file an issue on acme/webapp" — the skill drafts the issue, uploads the screenshot, and files it after your confirmation. ## Quick Start Attach a screenshot and ask the assistant to file a GitHub issue on your target repo describing the problem you see.

Frequently Asked Questions about file-github-issue

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

FAQPage Schema
How do I file a GitHub issue with a screenshot from the command line?

Use the gh CLI with gh issue create and a --body-file containing markdown. Since GitHub has no public API for inline issue attachments, commit the screenshot to a public repo via the Contents API and embed its raw URL in the body.

How do I attach images to GitHub issues programmatically?

GitHub's web paste-image flow uses a private endpoint, so the only API-reachable method is committing the image to a public repository with gh api and embedding the raw.githubusercontent.com URL in the issue markdown.

What image formats can I embed in a GitHub issue?

This skill accepts png, jpg, jpeg, gif, and webp files, all of which render inline in GitHub issue markdown. Other extensions are rejected with an error before filing.

Why does gh issue create fail with argument list too long?

Passing base64-encoded images as command-line arguments exceeds ARG_MAX around 100KB. Write the payload to a temp file and use jq --rawfile piped into gh api --input - so the content never touches argv.

What happens if the target repo is missing a label I want to apply?

The skill runs a label pre-flight with gh label list and intersects proposed labels with existing ones. Missing labels are dropped, shown in the preview, and flagged again after filing.

Can I file an issue without uploading the screenshot to a public repo?

Yes. If no attachments repo is configured, reply skip when prompted and the issue body embeds the screenshot's local file path instead, though it will not render inline for other viewers.