メニュー
ShipIt deployment architecture: auto-deploy on push via platform Git integration, GitHub Deployments API for status tracking, deployment status in PR lifecycle card. Load when working on deployment features.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Build, test, debug, and preview Android apps inside a ShipIt session. Load when a task touches an Android/Gradle project (Kotlin/Java, build.gradle(.kts), AndroidManifest.xml, res/ layouts, Compose UI). Covers the baked toolchain (JDK/SDK/Gradle), the build → lint → snapshot-test loop, reading snapshot PNG diffs, on-demand SDK installs, and the emulator-as-Compose-service for a live device over adb.
ShipIt React client architecture: Zustand stores, communication hooks (useApi, useSessionWebSocket, useServerEvents, useMessageHandler), component inventory, data flow patterns. Load when working on frontend components, stores, hooks, or client state.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
ShipIt git architecture: GitManager (per-session), RepoGit (shared bare cache + per-session local clones), credential setup, auto-commit flow, session clone lifecycle, branch naming. Load when working on git operations, the bare cache, per-session clones, credentials, or repo management.
ShipIt server/orchestrator architecture: buildApp(), HTTP API routes, services layer, WebSocket handler dispatch, SSE broadcasts, dependency injection, state scopes, manager initialization, type system. Load when working on orchestrator code, routes, services, or WebSocket handlers.
ShipIt Docker container and session runner architecture: ContainerSessionRunner, SessionRunnerRegistry, container creation/destruction, health monitoring, idle container disposal, reconnection after disposal, graceful shutdown. Load when working on containers, runners, idle cleanup, or container debugging.
| name | deployment-architecture |
| description | ShipIt deployment architecture: auto-deploy on push via platform Git integration, GitHub Deployments API for status tracking, deployment status in PR lifecycle card. Load when working on deployment features. |
| user-invocable | true |
ShipIt uses automatic deployments via platform Git integration — no manual deploy button or ShipIt-managed build. Users connect their repo to Vercel, Cloudflare Pages, or Netlify once, and every push triggers the platform's native deploy pipeline. Since ShipIt auto-pushes after every Claude turn, deploys happen automatically.
PrStatusPoller fetches deployment status via the GitHub GraphQL API| Component | Location | Role |
|---|---|---|
PrStatusPoller | orchestrator/pr-status-poller.ts | Polls GitHub for PR + deployment status |
GitHubDeploymentStatus | shared/types/deployment-types.ts | Type for deployment status data |
PrStatusSummary.deployments | shared/types/github-types.ts | Deployment data on PR status |
DeploymentStatusRow | client/components/PrLifecycleCard.tsx | UI row showing deploy status |
| Settings "Deployments" tab | client/components/Settings.tsx | Setup guide with platform links |
The PrStatusPoller GraphQL query includes commit.deployments(last:5) to fetch the latest
deployments for each PR's head commit. Each deployment includes:
This data is broadcast via SSE pr_status events and displayed in the PR lifecycle card's
DeploymentStatusRow component.
The Settings dialog has a "Deployments" tab under the "Project" section that shows:
No credentials are stored — the platform's own Git integration handles auth.