Menü
Manage semantic versions for npm packages
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
6-stage structured development cycle with stage-based tool restrictions
Multi-angle release quality verification using parallel expert review teams
Full Self Driving — autonomous release loop that processes all auto-dev-eligible GitHub issues until none remain, by repeatedly running /pipeline auto-dev then /homework.
Invoke and resume YAML-defined pipelines by name — /pipeline auto-dev runs the full release pipeline
Analyze release workflow findings and recommend follow-up actions — execute immediately or register as issues
Auto-detect project context and optimize harness — deactivate unused agents/skills, suggest missing experts, generate project profile
| name | omcustomcodex:npm-version |
| description | Manage semantic versions for npm packages |
| scope | package |
| argument-hint | <major|minor|patch> [--no-tag] [--no-commit] |
| disable-model-invocation | false |
| user-invocable | true |
Manage semantic versions for npm packages with automatic changelog and git integration.
major Bump major version (x.0.0)
minor Bump minor version (0.x.0)
patch Bump patch version (0.0.x)
--no-tag Skip git tag creation
--no-commit Skip commit creation (only update files)
1. Analyze current version from package.json
2. Determine version bump type
3. Update package.json version field
4. Update CHANGELOG.md if exists
5. Create version commit
6. Create git tag (optional)
[NPM Version] package-name
Previous: 1.2.3
Current: 1.2.4
Changes:
- package.json updated
- Commit: "chore: bump version to 1.2.4"
- Tag: v1.2.4
[NPM Version] Failed
Error: {error_message}
Hint: Ensure clean git working directory
# Bump patch version (1.2.3 -> 1.2.4)
npm-version patch
# Bump minor version (1.2.3 -> 1.3.0)
npm-version minor
# Bump major version (1.2.3 -> 2.0.0)
npm-version major
# Update version without creating git tag
npm-version patch --no-tag
When working with auto-tag.yml (automatic tag creation on release PR merge):
.npmrc has git-tag-version=false — prevents local tag creation during npm versionauto-tag.yml creates the tag on the merge commit when a release/* PR is merged to develop1. Create release branch: release/vX.Y.Z
2. Run version bump (npm version / manual edit) ← no local tag created
3. Build dist, commit, push
4. Create PR → merge to develop
5. auto-tag.yml creates vX.Y.Z tag on merge commit ← correct tag target
6. release.yml triggers on tag → GitHub Release + npm publish
If release/vX.Y.Z cannot be created because refs/heads/release exists:
git branch --list release --format='%(refname:short)'
git branch -m release releases-tracking # only after proving it is merged/backed up
If a tag already exists on remote (from a previous failed attempt):
git push origin :refs/tags/vX.Y.Z # delete remote tag
# Then re-merge or let auto-tag.yml handle it