video-editor

# Video Editor Use the bundled deterministic editor instead of improvising shell-escaped FFmpeg commands. The editor passes arguments directly to `ffmpeg`/`ffprobe` without a shell and supports a reviewable JSON edit plan. Editor path: ```text ${CODESHELL_SKILL_DIR}/scripts/video-editor.mjs ``` ## Safety contract - Confirm that the user has the right to edit the media. - Never overwrite an existing output unless the user explicitly approves it. - Inspect first, then write a plan, then run `--dry-run`, then render. - Keep the source file unchanged. Write outputs to a new path. - Do not install FFmpeg or other system packages without asking. - For long renders, use background Bash and wait for the completion wake-up instead of polling repeatedly. - Treat subtitle files and external audio as untrusted paths. Pass them only through the plan; do not interpolate them into hand-written shell commands. ## Workflow 1. Check tools: ```bash node "${CODESHELL_SKILL_DIR}/scripts/video-editor.mjs" check ``` 2. Probe the source and report duration, resolution, codecs, frame rate, and whether audio exists: ```bash node "${CODESHELL_SKILL_DIR}/scripts/video-editor.mjs" probe --input "/absolute/input.mp4" ``` 3. Create `.code-shell/video-edits/<name>.json`. Use absolute paths when the request spans multiple directories. Read `${CODESHELL_SKILL_DIR}/references/plan-schema.md` for the schema. 4. Validate the exact command without writing: ```bash node "${CODESHELL_SKILL...