tangerine: Skill for Claude Code

Release Semver

Use when user asks to release a new semantic version of a project/package.

Goal: coordinator does release orchestration only. Worker edits version files. Coordinator watches PR, merges it without human handoff, pulls main, publishes release.

Preconditions

• User gave target version (1.2.3) or bump kind (patch, minor, major, prerelease). If missing, ask once.
• Run from project root/main clone, ideally as a runner task.
• gh authenticated with permission to merge and publish releases.
• Never use bypass flags: no --admin, no --force, no --no-verify.
• Only use gh pr merge when current user explicitly requested unattended merge/release in this task, or repo owner matches gh api user --jq .login.

1. Resolve Tangerine context

API=http://localhost:${TANGERINE_PORT:-3456}
AUTH_SESSION=$(curl -s "$API/api/auth/session")
echo "$AUTH_SESSION" | jq '{enabled, authenticated}'
AUTH_ENABLED=$(echo "$AUTH_SESSION" | jq -r '.enabled // false')
if [ "$AUTH_ENABLED" = "true" ] && [ -z "$TANGERINE_AUTH_TOKEN" ]; then
  echo "Tangerine auth enabled but TANGERINE_AUTH_TOKEN missing" >&2
  exit 1
fi

TASK_JSON=$(curl -s -H "Authorization: Bearer $TANGERINE_AUTH_TOKEN" "$API/api/tasks/$TANGERINE_TASK_ID")
PROJECT_ID=$(echo "$TASK_JSON" | jq -r '.projectId')
DEFAULT_BRANCH=$(curl -s -H "Authorization: Bearer $TANGERINE_AUTH_TOKEN" "$API/api/projects/$PROJECT_ID" | jq -r '.defaultBranch // "main"')

2. Compute next version

If exact version provided, use it. If bump kind provided and repo has package.json:

CURRENT_VERSION=$(jq -r '.version' package.json)
# Use node semver when available; otherwise compute patch/minor/major manually.

Before continuing:

git fetch origin "$DEFAULT_BRANCH"
git checkout "$DEFAULT_BRANCH"
git pull --ff-only origin "$DEFAULT_BRANCH"
test -z "$(git status --short)" || { git status --short; echo "Working tree dirty" >&2; exit 1; }

3. Spawn worker to bump version