원클릭으로 Manus에서 모든 스킬 실행

deployment-architecture

스타4

포크0

업데이트2026년 3월 29일 17:18

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 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

nikzlabs

nikzlabs/shipit

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Deployment Architecture

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.

How It Works

User imports their GitHub repo on a hosting platform (Vercel, Cloudflare Pages, Netlify)
ShipIt's auto-push after Claude turns triggers the platform's deploy pipeline
The platform creates GitHub Deployments on each deploy
ShipIt's PrStatusPoller fetches deployment status via the GitHub GraphQL API
Deployment status (URLs, state) appears in the PR lifecycle card

Components

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

Deployment Status Tracking

The PrStatusPoller GraphQL query includes commit.deployments(last:5) to fetch the latest deployments for each PR's head commit. Each deployment includes:

environment — e.g. "Production", "Preview"
state — pending, success, failure, error, in_progress, etc.
environmentUrl — the deployed URL (preview or production)
creator — the platform that created the deployment (e.g. "vercel[bot]")

This data is broadcast via SSE pr_status events and displayed in the PR lifecycle card's DeploymentStatusRow component.

Setup Guide

The Settings dialog has a "Deployments" tab under the "Project" section that shows:

Links to import repos on Vercel, Cloudflare Pages, and Netlify
A brief explanation of how auto-deploy works with ShipIt

No credentials are stored — the platform's own Git integration handles auth.

Key Design Decisions

No manual deploy button — deploys happen on push, not on click
No ShipIt-managed builds — the platform runs its own build with its own env vars
GitHub Deployments API — platform-agnostic status tracking (works with any platform that creates GitHub Deployments)
No new credentials — uses the existing GitHub token from PR polling
PR card only — no toasts or notifications (deploys are frequent due to auto-push)

이 저장소의 다른 Skills

같은 저장소

android-build

nikzlabs/shipit

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.

2026-06-264

client-architecture

nikzlabs/shipit

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.

2026-06-104

frontend-design-frontend-design

nikzlabs/shipit

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.

2026-06-094

git-architecture

nikzlabs/shipit

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.

2026-06-084

server-architecture

nikzlabs/shipit

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.

2026-06-084

session-containers

nikzlabs/shipit

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.

2026-06-084

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

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