Create and edit Remotion GitHub issues, add comments, and attach images or videos. It keeps titles aligned with the user’s intent and checks saved issue text to ensure Markdown formatting and line breaks are preserved.
Create, edit, or comment on Remotion GitHub issues.
Review the instructions the agent will receive before you install.
Write a concise title that preserves the user's framing. An issue may describe a problem or give a directive; do not turn a problem into a prescribed solution unless the user supplied or explicitly requested one.
Prefix package-specific issues with the package name:
`@remotion/package`: Issue description
For broader areas, use the corresponding prefix:
Docs: Issue description
Studio: Issue description
Build: Issue description
CI: Issue description
Repo: Issue description
Avoid vague titles such as Bug, Fix issue, or Examples follow-up.
Never pass multiline Markdown inline through shell arguments. Write issue bodies and multiline comments to a temporary Markdown file, preferably with the write tool, and pass it with --body-file.
After creating or editing an issue, verify its title and body:
gh issue view <number> --json title,body
Confirm that the content is correct and multiline Markdown contains real newlines rather than literal \n sequences.
When the user provides an image or video, upload it with --attach on gh issue create, edit, or comment:
gh issue edit <number> --attach '/tmp/screenshot.png#Description of the screenshot'
Repeat the flag for multiple files. Images support alt text after #; videos do not. Attachments are appended, or matching local Markdown references are rewritten to uploaded URLs. Editing with only --attach preserves the existing body.
If an upload partially fails, inspect the issue before retrying to avoid duplicates. See gh issue <command> --help for details.
For parent issues, sub-issues, blocked-by, and blocking relationships, use the issue-management skill.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Add a reported Remotion bug to the bugs API with its affected versions, a short title, and upgrade guidance. Follow the existing entry format and place the new record first so recent bugs appear at the top.
Add a Remotion command-line or configuration option, or convert a hardcoded flag into a shared option definition. Connect parsing, configuration setters, help entries, and generated documentation so the option is consistently available and documented.
Add a new effect to @remotion/effects, including its implementation, package entry points, documentation, interactive demo, and preview images. Follow the package conventions and verify the changes with tests, formatting checks, and builds.
Add a person to the Remotion experts page by placing their portrait, entering their profile and contact links, and generating an expert card image. The instructions specify file locations, profile fields, and how to verify card generation.
Create a new @remotion package within the Remotion monorepo, a repository containing multiple packages. Set up its files, register it across the project, and prepare documentation, usage examples, and build configuration.
Add a new sound effect to @remotion/sfx, from registering the audio file to exporting its URL and documenting its use. The workflow covers playback examples, attribution, navigation entries, waveform generation, and the package build.