Turn a screen recording into a GitHub issue with AI
Record the bug once. Moonshot reads the recording and writes a GitHub-ready issue with a clear title, reproduction steps, expected and actual behavior, labels, and the recording link, then opens it in your repo.
A recording shows the bug. GitHub needs it written down
A screen recording is the fastest way to show a bug, but a GitHub issue still needs structure: a searchable title, reproduction steps, expected and actual behavior, environment, and labels so it can be triaged. Moonshot reads the recording and drafts that issue for you, so the reporter does not have to translate what they just recorded into markdown.
Every issue opens in a preset repo like acme/dashboard with the recording link attached as visual proof. That structure means faster bug resolution, because engineers get a testable issue instead of a link to a video.
How Moonshot creates a GitHub issue from a recording
Example GitHub issue from a Moonshot recording
Use Moonshot for every GitHub issue handoff
Whenever a bug is easier to show than to type, Moonshot turns the recording into a clean issue. For narrated code reviews rather than bug reports, see code walkthroughs, and browse the full set of integrations.
Turn exploratory testing recordings into consistent GitHub issues.
Record product issues while reviewing a build and open clean issues for engineering.
Convert customer issue walkthroughs into GitHub-ready engineering issues.
Point at a broken layout on screen and file it with visual proof.
Show what broke, where it broke, and how to reproduce it.
The same recording opens a Linear issue or Jira ticket too.
See the Linear integration →GitHub issue fields Moonshot helps fill
Moonshot vs Loom for GitHub issues
Be factual. Loom records great video and links out. Moonshot wins by turning the recording into a structured GitHub issue and opening it in your repo.
Questions, answered plainly
Can Moonshot create a GitHub issue from a screen recording?
Yes. Moonshot reads the recording and drafts a GitHub-ready issue, then opens it in your repository with the recording link attached.
What does Moonshot put in the GitHub issue?
A markdown body with title, description, reproduction steps, expected and actual behavior, environment, labels, and a recording link.
Can I choose the repository and labels?
Yes. You confirm the target repository, such as acme/dashboard, and add labels before the issue is opened.
Does the issue include console logs or network requests?
Moonshot focuses on visual recording, AI issue drafting, and structured handoff. If your team needs automatic logs or network capture, verify support before relying on it.