deploy

Run pre-flight git checks before deploying to GCE.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/neighbor-game-ai/DreamCore-V2-sandbox --skill deploy-neighbor-game-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy
Source: https://github.com/neighbor-game-ai/DreamCore-V2-sandbox/tree/main/.claude/skills/deploy
Command: npx skills add https://github.com/neighbor-game-ai/DreamCore-V2-sandbox --skill deploy-neighbor-game-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

デプロイ前の準備と検証を自動化し、コミット漏れや push の忘れを防ぎます。

Core Features & Use Cases

  • Pre-flight Checks: git status の状態と差分、現在のブランチ、最新コミットの確認を自動で実行します。
  • Phase-driven Deployment: 事前チェックをクリアした場合にのみ本番デプロイを実行します。
  • Health Checks & Rollback: デプロイ後のサービスヘルスを検証し、異常時には通知とロールバック手順を提供します。

Quick Start

Use the deploy skill to run pre-flight checks and deploy to production after confirming checks.

Frequently Asked Questions about deploy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate pre-flight checks before a production deployment?

Automating pre-flight checks involves validating git status, fetch status, branch state, and the latest commit before deploying. This ensures no un-pushed changes or missed commits reach production during your release workflow.

What happens if I forget to push commits before promoting staging to production?

If un-pushed changes or missed commits exist, the pre-flight deployment check blocks the release. It validates git status and fetch status to catch synchronization errors before any production deployment occurs.

Can I run a health check after deploying to GCE and rollback automatically?

Yes, after deploying to GCE, a health check phase verifies service health. If abnormalities are detected, it provides rollback procedures and notifications to ensure production stability.

How do I enforce branch validation during a CI-CD release workflow?

Enforcing branch validation during CI-CD requires checking the current branch and confirming the last commit details. This pre-flight step prevents deploying from incorrect or unverified branches to production.

What is the best way to prevent deployment mistakes when promoting changes across branches?

The best way to prevent deployment mistakes is running phase-driven pre-flight checks that enforce git status and branch validation. Only after clearing these checks does the production deployment proceed.