/versions
Check dependency versions and toolkit updates
$ npx -y skills add digitalsamba/claude-code-video-toolkit --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/versions
Context preview
What this command does when you run it.
Check dependency versions and toolkit updates
Command definition
versions.mddescription: Check dependency versions and toolkit updates
Versions
Check for version mismatches in project dependencies and toolkit updates.
Entry Point
On invocation, perform checks and present results:
Step 1: Detect Context
1. Check if in a project directory (has package.json with Remotion)
2. Read _internal/toolkit-registry.json for toolkit version
3. Determine what checks to run
Step 2: Run Checks
Project Dependency Check (if in project)
# Run Remotion's built-in version checker
npx remotion versions
Parse output for:
- Version mismatches between @remotion/* packages
- Any packages on different versions
Toolkit Version Check
1. Read current version from _internal/toolkit-registry.json
2. Fetch latest from GitHub API:
https://api.github.com/repos/digitalsamba/claude-code-video-toolkit/releases/latest
3. Compare versions
Step 3: Present Results
**All Good:**
Version Check
## Project: my-video
Remotion packages: 4.0.387 (all aligned)
## Toolkit
Current: v0.3.0
Latest: v0.3.0
Everything up to date.
**Issues Found:**
Version Check
## Project: my-video
Version mismatch detected:
| Package | Version |
|---------|---------|
| remotion | 4.0.383 |
| @remotion/cli | 4.0.383 |
| @remotion/google-fonts | 4.0.387 |
To fix: npx remotion upgrade
## Toolkit
Current: v0.2.0
Latest: v0.3.0
New in v0.3.0:
- Added transitions library
- New /design command
- Frontend-design skill
To upgrade:
git pull origin main
Actions:
→ Fix Remotion versions: 'fix'
→ View toolkit changelog: 'changelog'
---
Fix Flow
When user chooses to fix Remotion versions:
Step 1: Update package.json
1. Read package.json
2. Find all @remotion/* and remotion packages
3. Determine target version (latest installed or latest available)
4. Update all to same pinned version (no ^ prefix)
Step 2: Reinstall
rm -rf node_modules package-lock.json
npm install
Step 3: Verify
npx remotion versions
Step 4: Confirm
Fixed Remotion versions.
All packages now on: 4.0.387
Restart Remotion Studio to apply changes.
---
Toolkit Upgrade Flow
When upgrading toolkit:
Step 1: Check Git Status
git status --porcelain
If uncommitted changes:
You have uncommitted changes. Commit or stash before upgrading.
Modified files:
- project.json
- src/components/slides/TitleSlide.tsx
Options:
→ Stash changes: 'stash'
→ Cancel: 'cancel'
Step 2: Pull Updates
git pull origin main
Step 3: Show Changelog
Toolkit updated to v0.3.0
Changes:
- Added lib/transitions/ with 7 custom transitions
- New /design command for visual refinement
- Frontend-design skill for distinctive aesthetics
- Bug fixes in /scene-review
See _internal/CHANGELOG.md for full details.
Restart Claude Code to load new skills and commands.
---
Automatic Checks
Consider running version check automatically:
1. **On /video resume** - Check project before starting work 2. **Before render** - Warn if mismatches detected 3. **Weekly reminder** - Check for toolkit updates
These are suggestions for future enhancement.
---
Version Sources
| Component | Version Source | |-----------|----------------| | Toolkit | `_internal/toolkit-registry.json` → `version` | | Remotion | `node_modules/*/package.json` via `npx remotion versions` | | Latest toolkit | GitHub Releases API | | Latest Remotion | npm registry or `npx remotion upgrade --check` |
---
Common Issues
Remotion Version Mismatch
**Cause:** Using `^4.0.0` allows different minor versions to install independently.
**Prevention:** Pin exact versions in package.json:
{
"@remotion/cli": "4.0.387",
"remotion": "4.0.387"
}Toolkit Out of Date
**Cause:** Haven't pulled from upstream recently.
**Check:**
git fetch origin
git log HEAD..origin/main --oneline
---
Evolution
This command evolves through use. If something's awkward or missing:
**Local improvements:** 1. Say "improve this" → Claude captures in `_internal/BACKLOG.md` 2. Edit `.claude/commands/versions.md` 3. Share upstream → `gh pr create`
**Future ideas:**
- Check Node.js version compatibility
- Check Python tool dependencies
- Check ElevenLabs API version
- Automated weekly checks
Read more
description: Check dependency versions and toolkit updates
Versions
Check for version mismatches in project dependencies and toolkit updates.
Entry Point
On invocation, perform checks and present results:
Step 1: Detect Context
1. Check if in a project directory (has package.json with Remotion) 2. Read _internal/toolkit-registry.json for toolkit version 3. Determine what checks to run
Step 2: Run Checks
Project Dependency Check (if in project)
# Run Remotion's built-in version checker npx remotion versions
Parse output for:
- Version mismatches between @remotion/* packages
- Any packages on different versions
Toolkit Version Check
1. Read current version from _internal/toolkit-registry.json 2. Fetch latest from GitHub API: https://api.github.com/repos/digitalsamba/claude-code-video-toolkit/releases/latest 3. Compare versions
Step 3: Present Results
**All Good:**
Version Check ## Project: my-video Remotion packages: 4.0.387 (all aligned) ## Toolkit Current: v0.3.0 Latest: v0.3.0 Everything up to date.
**Issues Found:**
Version Check ## Project: my-video Version mismatch detected: | Package | Version | |---------|---------| | remotion | 4.0.383 | | @remotion/cli | 4.0.383 | | @remotion/google-fonts | 4.0.387 | To fix: npx remotion upgrade ## Toolkit Current: v0.2.0 Latest: v0.3.0 New in v0.3.0: - Added transitions library - New /design command - Frontend-design skill To upgrade: git pull origin main Actions: → Fix Remotion versions: 'fix' → View toolkit changelog: 'changelog'
---
Fix Flow
When user chooses to fix Remotion versions:
Step 1: Update package.json
1. Read package.json 2. Find all @remotion/* and remotion packages 3. Determine target version (latest installed or latest available) 4. Update all to same pinned version (no ^ prefix)
Step 2: Reinstall
rm -rf node_modules package-lock.json npm install
Step 3: Verify
npx remotion versions
Step 4: Confirm
Fixed Remotion versions. All packages now on: 4.0.387 Restart Remotion Studio to apply changes.
---
Toolkit Upgrade Flow
When upgrading toolkit:
Step 1: Check Git Status
git status --porcelain
If uncommitted changes:
You have uncommitted changes. Commit or stash before upgrading. Modified files: - project.json - src/components/slides/TitleSlide.tsx Options: → Stash changes: 'stash' → Cancel: 'cancel'
Step 2: Pull Updates
git pull origin main
Step 3: Show Changelog
Toolkit updated to v0.3.0 Changes: - Added lib/transitions/ with 7 custom transitions - New /design command for visual refinement - Frontend-design skill for distinctive aesthetics - Bug fixes in /scene-review See _internal/CHANGELOG.md for full details. Restart Claude Code to load new skills and commands.
---
Automatic Checks
Consider running version check automatically:
1. **On /video resume** - Check project before starting work 2. **Before render** - Warn if mismatches detected 3. **Weekly reminder** - Check for toolkit updates
These are suggestions for future enhancement.
---
Version Sources
| Component | Version Source | |-----------|----------------| | Toolkit | `_internal/toolkit-registry.json` → `version` | | Remotion | `node_modules/*/package.json` via `npx remotion versions` | | Latest toolkit | GitHub Releases API | | Latest Remotion | npm registry or `npx remotion upgrade --check` |
---
Common Issues
Remotion Version Mismatch
**Cause:** Using `^4.0.0` allows different minor versions to install independently.
**Prevention:** Pin exact versions in package.json:
{
"@remotion/cli": "4.0.387",
"remotion": "4.0.387"
}Toolkit Out of Date
**Cause:** Haven't pulled from upstream recently.
**Check:**
git fetch origin git log HEAD..origin/main --oneline
---
Evolution
This command evolves through use. If something's awkward or missing:
**Local improvements:** 1. Say "improve this" → Claude captures in `_internal/BACKLOG.md` 2. Edit `.claude/commands/versions.md` 3. Share upstream → `gh pr create`
**Future ideas:**
- Check Node.js version compatibility
- Check Python tool dependencies
- Check ElevenLabs API version
- Automated weekly checks
Tell Claude Code what video you want — it writes the script, generates the voiceover, music, and visuals, and renders the MP4.
Repo: digitalsamba/claude-code-video-toolkit
Other commands on claude-code-video-toolkit.
- /brand
Brand profiles - list, edit, or create new
Open command - /contribute
Share improvements - issues, PRs, skills, templates
Open command - /design
Focused design session for improving video scene visuals using the frontend-design skill.
Open command - /generate-voiceover
Generate AI voiceover from script
Open command - /publish
Publish a finished video to YouTube
Open command - /record-demo
Guided Playwright browser recording
Open command

