메뉴
Release a new version of outport. Use when the user says "release", "let's release", "tag a release", "ship it", "cut a release", "push a new version", or asks about the release process. Also use when the user asks to deploy docs after a release.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/steveclarke/outport --skill release명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Manage dev ports with Outport. Use when setting up a new project, adding services, resolving port conflicts, configuring monorepo cross-service URLs, or working with worktrees and multiple instances. Triggers on "outport", "port conflict", "port allocation", "dev ports", "outport.yml", "port management", "env var ports", "computed values", "cross-service URLs", "CORS origins from ports", ".test domains", "local DNS", "reverse proxy", "cookie isolation", "tunnel", "share localhost", "public URL", "cloudflare tunnel", "outport doctor", "health check", "diagnose outport", "QR code", "mobile access", "phone testing", "LAN IP", "hostname aliases", "multiple hostnames", "subdomain routing". Also use when the user mentions running multiple instances of a project, worktree port setup, or when services need to discover each other's URLs.
Audit all documentation for staleness after code changes. Checks README, CLAUDE.md, init presets, and release docs. Use after completing a feature, merging a PR, or when asked to check docs.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | release |
| description | Release a new version of outport. Use when the user says "release", "let's release", "tag a release", "ship it", "cut a release", "push a new version", or asks about the release process. Also use when the user asks to deploy docs after a release. |
Guides the release of a new outport version. Runs pre-flight checks, determines the version, tags, and deploys docs.
Verify master is clean and ready:
git checkout master
git pull
Check for uncommitted changes. If the working tree is dirty, stop and ask.
Run tests and lint:
just test
just lint
Both must pass before proceeding. If tests fail, stop and fix.
Check the latest tag:
git tag --sort=-v:refname | head -5
Look at what's changed since the last release:
git log --oneline $(git tag --sort=-v:refname | head -1)..HEAD
Suggest the next version based on what changed:
Present the suggestion with the commit list and ask the user to confirm the version number before proceeding.
git tag vX.Y.Z
git push origin vX.Y.Z
This triggers the GitHub Actions release workflow which builds binaries and updates the Homebrew tap.
Check if any docs changed since the last release:
git diff --name-only $(git tag --sort=-v:refname | head -2 | tail -1)..HEAD -- docs/ README.md
If docs changed, build and deploy:
npx vitepress build docs
npx wrangler pages deploy docs/.vitepress/dist --project-name outport-dev
If no docs changed, skip this step and say so.
Check the GitHub Actions run:
gh run list --limit 3
If the latest run is still in progress, let the user know and suggest they check back. If it completed, report the status.
Tell the user to verify the install when ready:
brew update && brew upgrade outport && outport --version