Skip to content
Back to skills

Version Sync Skill

ASecurity

Detect and synchronize Node.js version specifications across project files.

  • 2 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added May 26, 2026
developmentbashnodedockergit

Security analysis

A100/100

Pro scans all 5 files and shows the line behind each finding

Scanned May 27, 2026

npx -y skills add wrsmith108/claude-skill-version-sync --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Version Sync Skill?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Version Sync Skill
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/wrsmith108-version-sync-skill/badge)](https://www.skillsdirectory.com/skills/wrsmith108-version-sync-skill)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
# Version Sync Skill

Detect and synchronize Node.js version specifications across project files.

## Trigger Phrases

- "version mismatch"
- "upgrade node"
- "sync versions"
- "update node version"
- "version drift"
- "check node versions"
- "node version conflict"

## Commands

### Check Version Status

```bash
npx tsx scripts/index.ts check
```

Scans the current project for Node.js version specifications and reports any mismatches.

### Update All Versions

```bash
npx tsx scripts/index.ts update <version>
```

Updates all version files to the specified target version.

**Options:**
- `--dry-run` - Preview changes without modifying files

## Supported Files

| File | Pattern | Example |
|------|---------|---------|
| `.nvmrc` | First line number | `22` |
| `package.json` | `engines.node` | `">=22.0.0"` |
| `Dockerfile` | `FROM node:<version>` | `FROM node:22-slim` |
| `.github/workflows/*.yml` | `node-version` or `NODE_VERSION` | `node-version: '22'` |
| `docker-compose.yml` | `image: node:<version>` | `image: node:22-alpine` |

## Best Practices

1. Always run `check` first to understand current state
2. Use `--dry-run` before applying updates
3. Commit version changes separately for clear git history
4. Test after updating to ensure compatibility

Files in this skill

  • SKILL.md1.2 KB
  • package.json769 B
  • scripts/index.ts2.9 KB
  • scripts/version-check.ts8.4 KB
  • scripts/version-update.ts13 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.