redeploy

Orchestrate OmniNode post-release runtime redeploys with Docker and Infisical.

3|1|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/OmniNode-ai/omniclaude --skill redeploy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: redeploy
Source: https://github.com/OmniNode-ai/omniclaude/tree/main/plugins/onex/skills/redeploy
Command: npx skills add https://github.com/OmniNode-ai/omniclaude --skill redeploy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the complex and critical process of redeploying the OmniNode runtime after a new release, ensuring all components are updated, configured, and verified.

Core Features & Use Cases

  • Full Lifecycle Automation: Orchestrates syncing code, updating Docker configurations, rebuilding services, seeding secrets, and verifying system health.
  • Idempotent & Resumable: Designed to be safely re-run and to resume from the point of failure, minimizing downtime.
  • Use Case: After deploying a new version of the OmniClaude platform, use this Skill to seamlessly update the running services, ensuring the latest code and configurations are active and functional.

Quick Start

Run the redeploy skill to update the runtime to the latest versions detected from git tags.

Frequently Asked Questions about redeploy

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

FAQPage Schema
How do I orchestrate a full post-release runtime redeploy for the OmniNode platform?

Yes, the post-release runtime redeploy process is idempotent and resumable, meaning it can be safely re-run and will resume from the exact point of failure, minimizing downtime.

Can I skip specific phases or run a dry run during a Docker runtime redeploy?

This Skill updates Docker configurations by rebuilding the Docker runtime and updating Dockerfile plugin pins to ensure the latest code and configurations are active and functional.

What's the best way to verify system health endpoints and package versions after a deploy?

Infisical is integrated into the deployment process to seed new contract keys, ensuring all updated services have the correct configurations and secrets synced during the runtime redeploy.

Why does my post-release deployment fail when updating Docker runtime configurations?

A bare clone synchronization ensures your local repository matches the remote state before updating Docker configurations, preventing inconsistencies during the runtime redeploy.