issue

Name: issue
Author: remotion-dev

54kstars3.9kforks

How to install issue?

remotion-dev/remotion/issue

$npx -y skills add remotion-dev/remotion --skill issue

Installs into the current project.

Summary

Create or update GitHub issues with correct Remotion naming and safe multiline Markdown handling

Files · 1

View on GitHub

SKILL.md

1	Use this skill when creating, editing, or commenting on GitHub issues. For parent issues, sub-issues, blocked-by, and blocking relationships, use the [`issue-management`](../issue-management/SKILL.md) skill.
2
3	## Issue title format
4
5	Use concise, action-oriented titles.
6
7	If the issue primarily affects a package, prefix the title with the package name:
8
9	```text
10	`@remotion/package`: Change description
11	```
12
13	Examples:
14
15	```text
16	`@remotion/player`: Support keyboard shortcuts for fullscreen
17	`@remotion/lambda`: Improve retry message for failed renders
18	`@remotion/docs`: Add examples contribution guide
19	```
20
21	If the issue affects the website/docs broadly, use:
22
23	```text
24	Docs: Change description
25	```
26
27	If the issue affects the Studio broadly, use:
28
29	```text
30	Studio: Change description
31	```
32
33	If the issue affects the monorepo or infrastructure broadly, use:
34
35	```text
36	Build: Change description
37	CI: Change description
38	Repo: Change description
39	```
40
41	Avoid vague titles such as:
42
43	```text
44	Bug
45	Fix issue
46	Examples follow-up
47	```
48
49	Prefer:
50
51	```text
52	Docs: Add a skill for creating examples
53	```
54
55	## Never pass multiline Markdown inline
56
57	Do not pass issue bodies, PR bodies, or long comments inline through shell arguments.
58
59	Avoid:
60
61	```bash
62	gh issue create --title "Docs: Add examples skill" --body "Line one\n\nLine two"
63	```
64
65	This can accidentally send literal `\n` characters to GitHub instead of real newlines.
66
67	Instead, always write Markdown to a temporary file and pass it with `--body-file`.
68
69	## Creating an issue
70
71	1. Write the issue body to a temp Markdown file:
72
73	```bash
74	cat > /tmp/remotion-issue-body.md <<'EOF'
75	Summary of the issue.
76
77	## Tasks
78
79	- [ ] First task
80	- [ ] Second task
81
82	## Context
83
84	Related to #1234.
85	EOF
86	```
87
88	2. Create the issue using `--body-file`:
89
90	```bash
91	gh issue create \
92	--title 'Docs: Add a skill for creating examples' \
93	--body-file /tmp/remotion-issue-body.md
94	```
95
96	Prefer using the `write` tool to create the temp Markdown file instead of shell heredocs when operating as an agent.
97
98	## Editing an issue body
99
100	1. Write the full replacement body to a temp Markdown file.
101	2. Edit the issue using `--body-file`:
102
103	```bash
104	gh issue edit 1234 --body-file /tmp/remotion-issue-body.md
105	```
106
107	After editing, verify that the body renders as intended:
108
109	```bash
110	gh issue view 1234 --json body --jq .body
111	```
112
113	Make sure the output contains real blank lines, not literal `\n` escape sequences.
114
115	## Adding an issue comment
116
117	For multiline comments, also use a file:
118
119	```bash
120	gh issue comment 1234 --body-file /tmp/remotion-issue-comment.md
121	```
122
123	## Creating or linking related issues
124
125	For parent issues, sub-issues, blocked-by, and blocking relationships, use the [`issue-management`](../issue-management/SKILL.md) skill. Prefer the new `gh issue create` and `gh issue edit` relationship flags over hand-written GraphQL mutations.
126
127	## Updating a PR or issue after linking a related issue
128
129	If a PR or issue mentions follow-up work that is now tracked by a related issue, replace vague checklist items with the concrete issue number.
130
131	Prefer:
132
133	```md
134	The Remotion skill for creating examples is tracked separately in sub-issue #8158, not in this PR.
135	```
136
137	Avoid:
138
139	```md
140	- [ ] Add a Remotion skill for creating an example
141	```
142
143	if that work is not part of the current PR.
144
145	## Final verification checklist
146
147	After creating or editing an issue:
148
149	- [ ] View the issue body with `gh issue view <number> --json body --jq .body`
150	- [ ] Confirm Markdown has real newlines
151	- [ ] Confirm the title follows the package/docs/studio naming convention
152	- [ ] Confirm issue references such as `#1234` are correct
153	- [ ] If adding issue relationships, follow the `issue-management` skill and confirm the intended links

People who liked this also viewed

6 picks

Type

paperclip-create-agentCreate new agents in Paperclip with governance-aware hiring. Use when you need to inspect adapter configuration options, compare existing agent configs, draft a new agent prompt/config, and submit a hSkillsJul 2026157k5
subagent-driven-developmentUse when executing implementation plans with independent tasks in the current sessionSkillsJul 2026154k259k
dispatching-parallel-agentsUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesSkillsJul 2026143k259k
browser-act-skill-forgeForges reusable Skill packages (SKILL.md + scripts) from website exploration via browser-act — no re-exploration later. Use when: user wants a reusable Skill for any website, needs to understand a sitSkillsJul 202685k4.6k
wizardGenerate an interactive bash wizard that walks a human through a manual procedure — third-party setup, a one-off migration, an A→B state transition — opening URLs, capturing values, confirming each stSkillsJul 202675k182k
wonda-cliUsing the Wonda CLI to generate images, videos, music, and audio from the terminal — plus LinkedIn, Reddit, and X/Twitter research and automationSkillsJul 202666k137

issue

54kstars3.9kforks

View on GitHub

How to install issue?

remotion-dev/remotion/issue

$npx -y skills add remotion-dev/remotion --skill issue

Installs into the current project.

Summary

Create or update GitHub issues with correct Remotion naming and safe multiline Markdown handling

Files · 1

View on GitHub

SKILL.md

1	Use this skill when creating, editing, or commenting on GitHub issues. For parent issues, sub-issues, blocked-by, and blocking relationships, use the [`issue-management`](../issue-management/SKILL.md) skill.
2
3	## Issue title format
4
5	Use concise, action-oriented titles.
6
7	If the issue primarily affects a package, prefix the title with the package name:
8
9	```text
10	`@remotion/package`: Change description
11	```
12
13	Examples:
14
15	```text
16	`@remotion/player`: Support keyboard shortcuts for fullscreen
17	`@remotion/lambda`: Improve retry message for failed renders
18	`@remotion/docs`: Add examples contribution guide
19	```
20
21	If the issue affects the website/docs broadly, use:
22
23	```text
24	Docs: Change description
25	```
26
27	If the issue affects the Studio broadly, use:
28
29	```text
30	Studio: Change description
31	```
32
33	If the issue affects the monorepo or infrastructure broadly, use:
34
35	```text
36	Build: Change description
37	CI: Change description
38	Repo: Change description
39	```
40
41	Avoid vague titles such as:
42
43	```text
44	Bug
45	Fix issue
46	Examples follow-up
47	```
48
49	Prefer:
50
51	```text
52	Docs: Add a skill for creating examples
53	```
54
55	## Never pass multiline Markdown inline
56
57	Do not pass issue bodies, PR bodies, or long comments inline through shell arguments.
58
59	Avoid:
60
61	```bash
62	gh issue create --title "Docs: Add examples skill" --body "Line one\n\nLine two"
63	```
64
65	This can accidentally send literal `\n` characters to GitHub instead of real newlines.
66
67	Instead, always write Markdown to a temporary file and pass it with `--body-file`.
68
69	## Creating an issue
70
71	1. Write the issue body to a temp Markdown file:
72
73	```bash
74	cat > /tmp/remotion-issue-body.md <<'EOF'
75	Summary of the issue.
76
77	## Tasks
78
79	- [ ] First task
80	- [ ] Second task
81
82	## Context
83
84	Related to #1234.
85	EOF
86	```
87
88	2. Create the issue using `--body-file`:
89
90	```bash
91	gh issue create \
92	--title 'Docs: Add a skill for creating examples' \
93	--body-file /tmp/remotion-issue-body.md
94	```
95
96	Prefer using the `write` tool to create the temp Markdown file instead of shell heredocs when operating as an agent.
97
98	## Editing an issue body
99
100	1. Write the full replacement body to a temp Markdown file.
101	2. Edit the issue using `--body-file`:
102
103	```bash
104	gh issue edit 1234 --body-file /tmp/remotion-issue-body.md
105	```
106
107	After editing, verify that the body renders as intended:
108
109	```bash
110	gh issue view 1234 --json body --jq .body
111	```
112
113	Make sure the output contains real blank lines, not literal `\n` escape sequences.
114
115	## Adding an issue comment
116
117	For multiline comments, also use a file:
118
119	```bash
120	gh issue comment 1234 --body-file /tmp/remotion-issue-comment.md
121	```
122
123	## Creating or linking related issues
124
125	For parent issues, sub-issues, blocked-by, and blocking relationships, use the [`issue-management`](../issue-management/SKILL.md) skill. Prefer the new `gh issue create` and `gh issue edit` relationship flags over hand-written GraphQL mutations.
126
127	## Updating a PR or issue after linking a related issue
128
129	If a PR or issue mentions follow-up work that is now tracked by a related issue, replace vague checklist items with the concrete issue number.
130
131	Prefer:
132
133	```md
134	The Remotion skill for creating examples is tracked separately in sub-issue #8158, not in this PR.
135	```
136
137	Avoid:
138
139	```md
140	- [ ] Add a Remotion skill for creating an example
141	```
142
143	if that work is not part of the current PR.
144
145	## Final verification checklist
146
147	After creating or editing an issue:
148
149	- [ ] View the issue body with `gh issue view <number> --json body --jq .body`
150	- [ ] Confirm Markdown has real newlines
151	- [ ] Confirm the title follows the package/docs/studio naming convention
152	- [ ] Confirm issue references such as `#1234` are correct
153	- [ ] If adding issue relationships, follow the `issue-management` skill and confirm the intended links

People who liked this also viewed

6 picks

Type