Agent skill · remotion-dev
no-comments
Remove code comments that explain or defend Remotion's own code, keeping only comments about external systems we cannot change (browser quirks, codec/FFmpeg behavior, third-party APIs, OS or platform bugs). Use when the user invokes /no-comments or asks to strip unnecessary comments from a diff or files.
What it needs
About 2k tokens when loaded.
What this skill does
No comments Delete comments that describe our own code. Code we own should explain itself through names, types, and structure. Keep a comment only when it documents something outside our control that a reader could not learn from our code. Scope Use the files or diff the user named. Otherwise use the current diff against main, including staged, unstaged, and untracked changes: Only touch comments on lines added or modified in scope. Do not sweep untouched code in the same file. Keep A comment stays only if it is about an external system and is still accurate: Browser behavior: Chrome/Safari/Firefox quirks, WebCodecs, Canvas, CSS, layout, event ordering, autoplay policy, linked bug trackers. Media and tooling: FFmpeg, codecs, containers, Mediabunny, Chromium flags, Lambda/Cloud Run limits, Node.js, Bun, TypeScript compiler, bundler behavior. Third-party libraries and APIs: why we call them in an unusual way, links to upstream issues. OS, hardware, and spec constraints: file system, GPU, Linux/macOS/Windows differences, RFCs, W3C specs. Also keep: Machine-read directives: eslint-disable, @ts-expect-error, @ts-ignore, /// <reference>, 'use client', istanbul ignore, prettier-ignore, biome-ignore, @vitest-environment, shebangs, license headers. Still check that each suppression is needed; remove dead ones. JSDoc on public exported APIs (it surfaces in editor tooltips). @deprecated tags (see the deprecate-api skill). Comments in docs, MDX, and code snippets that are shown to users. Delete Narration of what the next lines do (// Get the frame, // Loop over tracks). Restating names, types, or parameters. Explanations of our own architecture, data flow, or design choices. Defenses of workarounds for our own bugs. Fix the root cause in scope or leave the code uncommented. IMPORTANT, do not remove, keep in sync with X, talk to Y first notes about our own code. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills remotion-dev/no-comments