build-deploy

Rebuild Ark and restart the claude-code-ark service under PM2.

2|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/ignission/claude-code-ark --skill build-deploy-ignission
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-deploy
Source: https://github.com/ignission/claude-code-ark/tree/main/.claude/skills/build-deploy
Command: npx skills add https://github.com/ignission/claude-code-ark --skill build-deploy-ignission

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ark builds and deploys the Claude Code Ark stack by automating a clean build, process restart, and service recovery with deterministic steps.

Core Features & Use Cases

  • Automated Build & Restart: Rebuild Ark and restart the managed process to ensure a fresh, stable deployment.
  • Graceful Process Handling: Stops conflicting ttyd processes before rebuild to avoid port collisions.
  • Operational Guidance: Provides clear success/failure reporting for quick issue resolution in DevOps workflows.

Quick Start

Rebuild Ark and restart the service with pm2 using the provided steps in this skill.

Frequently Asked Questions about build-deploy

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

FAQPage Schema
How do I automate a pnpm build and PM2 restart for my DevOps workflow?

To automate a pnpm build and PM2 restart, this skill executes a deterministic sequence that stops conflicting ttyd processes, runs the build, and relaunches the claude-code-ark service. It validates results to ensure a clean deployment with minimal downtime.

Why does my claude-code-ark deployment fail with port conflicts during a PM2 restart?

Port conflicts during a claude-code-ark deployment often occur when ttyd processes are still running. This build and deploy skill handles graceful process termination by stopping ttyd before rebuilding, preventing port collisions and ensuring a successful PM2 service restart.

What is the best way to ensure minimal downtime when rebuilding a Node.js application with PM2?

The best way to ensure minimal downtime during a Node.js rebuild is to enforce a deterministic deployment sequence. This skill automates stopping ttyd, running pnpm build, and restarting the PM2 service, validating each step for quick issue resolution.

Can I add custom pre-deployment or post-deployment steps to a PM2 build pipeline?

Yes, you can extend the PM2 build pipeline with optional pre and post steps. The core deployment sequence stops ttyd, runs pnpm build, and restarts claude-code-ark, while supporting extensions for additional DevOps operations before or after the build.

Does this automated build and deploy process provide success or failure reporting for DevOps?

Yes, the automated build and deploy process provides clear operational guidance with success and failure reporting. This allows DevOps teams to quickly identify and resolve issues during the pnpm build and PM2 restart sequence.

Do I need to manually stop ttyd before running pnpm build for claude-code-ark?

No, you do not need to manually stop ttyd before running pnpm build. The automated deployment sequence gracefully stops conflicting ttyd processes before rebuilding claude-code-ark to avoid port collisions and ensure a clean PM2 restart.