[pull] main from remotion-dev:main

.claude/commands/release.md

@@ -8,3 +8,11 @@
 - Check `https://www.npmjs.com/package/remotion` to get the current version number
 - Run `bun set-version.ts <version>`, where <version> is the current version plus 1
 - Run `NPM_CONFIG_TOKEN=<token> bun run release` where <token> is the NPM token we just created
+- Generate a changelog in markdown and save it to `/tmp/release-<version>.md`:
+  - Run `git log v<previous_version>..v<new_version> --oneline` to get all commits
+  - Extract PR numbers from merge commits
+  - For each PR, run `gh pr view <number> --json title,author,number,url --jq '"* \(.title) by @\(.author.login) in \(.url)"'`
+  - Categorize PRs into sections: "What's Changed" (features, fixes, improvements), "Internal" (dependency upgrades, tooling, infra), "Docs" (documentation changes), "Templates" (template changes)
+  - Check for new contributors by comparing authors against known contributors
+  - Add `**Full Changelog**: https://github.com/remotion-dev/remotion/compare/v<previous_version>...v<new_version>` at the bottom
+  - Use the same format as previous GitHub releases (check with `gh release view v<previous_version>`)

.claude/skills/add-cli-option/SKILL.md

@@ -75,17 +75,19 @@ For Studio options, this is typically in `packages/cli/src/studio.ts`. For rende
 - Add the setter signature to the `FlatConfig` type (either in the `RemotionConfigObject` global interface or the `FlatConfig` intersection)
 - Add the implementation to the `Config` object: `setMyFlagEnabled: myFlagOption.setConfig`
 
-## 6. Update docs
+## 6. Update docs — IMPORTANT, do not skip this step
 
-In the relevant CLI command page:
+**This step is mandatory.** Every new option must have its docs updated to use `<Options id="..." />` so the description is pulled from the option definition automatically (single source of truth). If converting an existing hardcoded flag, replace any hand-written description with the `<Options>` component.
 
-- Add a `### \`--my-flag\`` section
-- Use `<Options id="my-flag" />` to pull the description from the option definition automatically
-- The `id` matches the option's `cliFlag` value
+**CLI command pages** (check all that apply — `cli/render.mdx`, `lambda/cli/render.mdx`, `cloudrun/cli/render.mdx`, `cli/benchmark.mdx`):
+
+- Add or update the `### \`--my-flag\`` section
+- Use `<Options id="my-flag" />` as the description body (no import needed — it's globally available)
+- The `id` must match the option's `cliFlag` / `id` value
 
 **`packages/docs/docs/config.mdx`**:
 
-- Add a `## \`setMyFlagEnabled()\`` section with:
+- Add or update the `## \`setMyFlagEnabled()\`` section with:
   - `<Options id="my-flag" />` for the description
   - A twoslash config example
   - A note that the CLI flag takes precedence