run-deploy

Trigger GitHub Actions deployments and verify post-deploy health.

5|1|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/mataeil/OODA-loop --skill run-deploy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-deploy
Source: https://github.com/mataeil/OODA-loop/tree/main/skills/run-deploy
Command: npx skills add https://github.com/mataeil/OODA-loop --skill run-deploy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the risky and error-prone process of initiating deployments by coordinating checks, triggering workflows, and ensuring post-deploy health.

Core Features & Use Cases

  • Pre-deploy safety checks: HALT presence, health indicators, and configuration validation prevent unintended deployments.
  • Workflow orchestration: Fires GitHub Actions via workflow_dispatch and passes optional inputs.
  • Observation & verification: Monitors the workflow, handles timeouts, and validates service health after deployment.
  • State reporting: Writes standardized deployment state to agent/state/deploy.json for auditability.

Quick Start

Run the run-deploy workflow in your repository to start a deployment and observe its outcome.

Frequently Asked Questions about run-deploy

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

FAQPage Schema
How do I safely trigger GitHub Actions deployments via workflow_dispatch?

To safely trigger GitHub Actions deployments via workflow_dispatch, you must validate pre-deploy conditions and safety checks before firing the workflow. This process monitors completion and verifies post-deploy health across branches and environments.

What pre-deploy safety checks are needed to prevent unintended GitHub Actions deployments?

Pre-deploy safety checks include verifying HALT presence, checking health indicators, and performing configuration validation. These checks prevent unintended deployments by ensuring all conditions are met before firing the GitHub Actions workflow.

How do I monitor a GitHub Actions workflow and verify service health after deployment?

You monitor a GitHub Actions workflow by tracking its completion status and handling timeouts during execution. After deployment, you verify service health by checking post-deploy health indicators across branches and environments.

Does triggering GitHub Actions deployments require gh CLI authentication?

Yes, triggering GitHub Actions deployments requires the gh CLI to be available and authenticated. The deployment process enforces this safety check before firing the configured workflow to ensure secure workflow_dispatch execution.

Why do I need to record a structured deployment state when automating GitHub Actions?

Recording a structured deployment state when automating GitHub Actions provides auditability for your deployment process. It writes standardized deployment state with timing and run details to agent/state/deploy.json for tracking purposes.