메뉴
Create a new version release for vidpipe. Use this skill when asked to release, version, tag, or create a new version. Handles version bump, changelog generation, GitHub release, and npm publishing.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Manage Late.co social media scheduling API — list, reschedule, bulk delete, and sync scheduled posts. Use this skill when asked to manage scheduled posts, clean up the Late queue, reschedule posts, inspect Late API state, or troubleshoot Late API issues.
Review and inspect video files using Gemini AI vision. Use this skill when asked to inspect, review, analyze, describe, or understand what's happening in a video file. Supports custom prompts for targeted analysis.
Publish packages to npm registry. Use this skill when asked to publish, release, or deploy a package to npm. Handles granular access token creation, authentication, and publishing with 2FA bypass.
| name | release |
| description | Create a new version release for vidpipe. Use this skill when asked to release, version, tag, or create a new version. Handles version bump, changelog generation, GitHub release, and npm publishing. |
Complete workflow for creating a new versioned release of vidpipe, including version bump, release notes, GitHub release, and npm publishing.
git status shows no uncommitted changes)npm test)gh CLI authenticated (gh auth status)Check commits since the last tag to decide the bump type:
git log --oneline $(git describe --tags --abbrev=0)..HEAD
fix: commits)feat: commits), no breaking changesBREAKING CHANGE or !: commits)npm version <patch|minor|major> --no-git-tag-version
This updates package.json and package-lock.json without creating a git tag (we'll do that manually after release notes).
npm run build && npm test
All tests must pass before proceeding.
git add package.json package-lock.json
git commit -m "chore: bump version to <NEW_VERSION>"
git push origin main
git tag -a v<NEW_VERSION> -m "v<NEW_VERSION>"
git push origin v<NEW_VERSION>
Write release notes that include:
feat: commits) — describe what's new with user-facing impactfix: commits) — describe what was broken and how it's fixedFormat as GitHub-flavored markdown with emoji section headers (✨ Features, 🐛 Fixes, 📖 Documentation, 🔧 Internal).
Include a changelog link at the bottom:
**Full Changelog**: https://github.com/htekdev/vidpipe/compare/vOLD...vNEW
gh release create v<NEW_VERSION> --title "v<NEW_VERSION> — <SHORT_DESCRIPTION>" --notes "<RELEASE_NOTES>"
Follow the npm-publish skill:
npm config set //registry.npmjs.org/:_authToken=<TOKEN>npm publish --access publicnpm view vidpipe versionnpm config delete //registry.npmjs.org/:_authTokenIf no token is available, use Playwright to create one (see npm-publish skill).
gh release view v<NEW_VERSION>npm view vidpipe version--no-git-tag-version with npm version to separate the version bump commit from the tag