Screenshots and videos you mention are uploaded with gh issue create --attach, or GitHub’s upload endpoint as a fallback, then the filed issue is read back to confirm no local path is left behind.
GitHub issue filer
One request.
One complete issue.
gh-create turns a quick request into an issue another person or agent can act on, and files it the same way no matter which agent you asked.
and its visibility
helps (optional)
assign, attach
check how it renders
Same issue, any agent
Expanded, but never rewritten away.
The agent writes a structured issue: a summary, steps to reproduce or numbered requirements, expected and actual behavior, and acceptance criteria. Your original prompt is quoted word for word at the bottom, so the issue can be reproduced, replayed, and audited.
It applies every label the repository already has that fits, such as kind, platform, and area, and never invents one. It assigns the issue to you with @me unless you ask for someone else or for nobody.
Crash when saving an empty file
bug · windows · ui · assigned to you
The hard parts, written down
Media that renders. Secrets that don’t.
Local paths, names, emails, hostnames, and tokens stay out, even in the quoted prompt. A public issue never mentions a private repository or its code.
With the repository at hand it can point to the files involved and link related issues, but it never holds up filing.
Install separately
Give every agent the same issue template.
skills.sh
Install for your selected agents in one command.
npx --yes skills add lsegal/glorp@gh-create --global --agent codex --agent claude-code --agent gemini-cli --agent opencode --agent cline --agent universal -yGitHub CLI
Install the bundled skill directly for your agent.
gh skill install lsegal/glorp gh-create --allow-hidden-dirs --agent codex --agent claude-code --scope userRun it/gh-create owner/repo the save button crashes on empty files, see ./crash.png