원클릭으로
publish
Publish a new version via GitHub Actions. Use when user says "publish", "release", or "bump version".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Publish a new version via GitHub Actions. Use when user says "publish", "release", or "bump version".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Create and manage local Issue specs (specs/issues/) - individual work items with testable acceptance criteria. Use for "create issue", "new task", "list issues", "check issues", "pick issue". NOTE - For GitHub issues, use `gh issue` command directly.
Create and manage Epics - collections of related issues for major feature areas. Use when starting a new project(big feature), organizing work into themes, or adding reference documents.
Generate Conventional Commits 1.0.0 compliant messages. Use when the user says "commit", "create commit", or finishes implementing code.
| name | publish |
| description | Publish a new version via GitHub Actions. Use when user says "publish", "release", or "bump version". |
Automate version bumping and release via GitHub Actions workflow.
/publish [version-type]
/publish - Auto-detect version type from commits (default: patch)/publish patch - Bug fixes (0.0.X)/publish minor - New features (0.X.0)/publish major - Breaking changes (X.0.0)/publish 1.2.3 - Specific version number1. PRE-FLIGHT CHECK → Verify clean working tree, on main branch
↓
2. ANALYZE CHANGES → Review commits since last tag to suggest version
↓
3. BUMP VERSION → Update package.json version
↓
4. COMMIT & TAG → Create release commit and git tag
↓
5. PUSH → Push commit and tag to trigger CI/CD
# Verify clean state
git status --porcelain
git branch --show-current
# Get current version and last tag
cat packages/cli/package.json | grep '"version"'
git describe --tags --abbrev=0 2>/dev/null || echo "No tags yet"
STOP if:
# Show commits since last tag
git log $(git describe --tags --abbrev=0 2>/dev/null || echo "HEAD~10")..HEAD --oneline
# Look for version indicators
# - "feat:" or "feat!:" → minor or major
# - "fix:" → patch
# - "BREAKING CHANGE" → major
Suggest version type based on conventional commits:
| Commit Type | Version Bump |
|---|---|
fix: | PATCH |
feat: | MINOR |
feat!: or BREAKING CHANGE | MAJOR |
# Read current version
CURRENT=$(grep '"version"' packages/cli/package.json | sed 's/.*"version": "\(.*\)".*/\1/')
echo "Current version: $CURRENT"
# Calculate new version (or use user-specified)
# For patch: 0.1.5 → 0.1.6
# For minor: 0.1.5 → 0.2.0
# For major: 0.1.5 → 1.0.0
Edit packages/cli/package.json to update the version.
Use conventional commit format:
git add packages/cli/package.json
git commit -m "chore(cli): bump version to X.Y.Z"
git tag vX.Y.Z
DO NOT add Claude Code references or co-author tags.
git push origin main vX.Y.Z
Provide the GitHub Actions URL for monitoring:
https://github.com/skilluse/skilluse/actions
// Parse semver: "0.1.5" → [0, 1, 5]
const [major, minor, patch] = version.split('.').map(Number);
// Bump logic
patch: `${major}.${minor}.${patch + 1}`
minor: `${major}.${minor + 1}.0`
major: `${major + 1}.0.0`
| Issue | Action |
|---|---|
| Uncommitted changes | Ask user to commit or stash first |
| Not on main | Warn and ask for confirmation |
| Tag already exists | Suggest next version |
| Push fails | Check remote access, show error |
After workflow completes, users can verify:
npm install -g skilluse
skilluse --version