physics91

Use when publishing or releasing openrouter-mcp to npm, or preparing a version for distribution with metadata and release checks

Use when installing or repairing Claude Desktop or Claude Code MCP config, checking status, backing up config files, or fixing config drift in openrouter-mcp

Use when changing concurrency limits, quota rules, circuit breakers, cleanup behavior, or other high-risk resilience policies in the collective-intelligence paths

Use when handling API key setup, credential rotation or deletion, security-audit runs, shared-environment risk checks, or security-document hygiene in openrouter-mcp

Use when running tests, reproducing the repository's assurance gate locally, checking failures, or verifying coverage for openrouter-mcp

Use when checking code quality, running linting, formatting code, or verifying static analysis gates before PR or publish.

Use when the user asks to continue with additional tasks while keeping current work in progress, or needs parallel branch development, hotfix interruption handling, and review sandboxes without extra clones. Use when tasks involve `git worktree add/list/remove/prune/lock/repair`, resolving branch-in-use conflicts across worktrees, configuring per-worktree settings (`git config --worktree`, `extensions.worktreeConfig`), or writing scripts that must resolve worktree paths safely with `git rev-parse`.

Use when setting up or troubleshooting naverworks CLI multi-profile authentication, including profile creation, OAuth/JWT login, and CI/CD auth configuration. Triggers on "naverworks 프로필", "naverworks 인증", "NW_PROFILE". If the task is executing NAVER WORKS API commands, use the naverworks-cli skill. If the task is build or release automation, use the build or deploy skill.

Use when adding or refactoring `naverworks-cli` commands or internals and you need to manage project-specific code reuse, helper extraction, duplication cleanup, or reuse exceptions. Reviews hotspot-heavy `cmd/` and `internal/` code, decides whether to reuse an existing helper, extract a new shared helper, keep logic local, or grant a time-bounded waiver, and records catalog/lifecycle/scorecard updates. If you only need build, test, deploy, release, version, profile, or commit workflows, use the existing project-local skills instead.

Use when releasing a new version of naverworks — runs preflight checks, creates and pushes a SemVer tag, and verifies the GitHub Actions release workflow that builds artifacts and publishes npm packages. Triggers on "배포", "릴리스", "deploy", "release", "/deploy". If you only need to inspect or create tags, use version. If you only need local binaries, use build.

Use when building naverworks binaries — single-platform or cross-platform artifacts with ldflags version metadata. Triggers on "빌드", "build", "/build". If you need test results only, use the test skill. If you need to publish a release tag, use deploy or version.

Use when verifying the naverworks codebase — runs unit, integration, and e2e test layers with go test, go vet, and build smoke check. Triggers on "테스트", "test", "/test". Covers test pyramid (unit/integration/e2e) with real functionality verification. For local binaries, use build. For releasing, use deploy. For managing existing releases, use release. For version inspection or tag creation, use version.

Use when inspecting naverworks version state or creating/pushing release tags directly. Triggers on "버전", "version", "/version", "bump". If you want guarded preflight checks plus release monitoring, use deploy. If you only need local binaries, use build.

Manage GitHub Releases for naverworks — view, edit, delete, and rollback published releases using gh CLI. Triggers on "릴리스 관리", "release manage", "release edit", "release delete", "release rollback". If you need to create a new release (tag + push + publish), use deploy. For local binaries, use build. For running tests, use test. For version inspection or tag creation, use version.