deploy-kuro

Run pre-flight checks, commit changes, monitor CI/CD, and verify Kuro service health.

3|1|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/miles990/mini-agent --skill deploy-kuro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy-kuro
Source: https://github.com/miles990/mini-agent/tree/main/.claude/skills/deploy-kuro
Command: npx skills add https://github.com/miles990/mini-agent --skill deploy-kuro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents risky Kuro deployments by enforcing a repeatable checklist that validates code quality, cross-layer consistency, service health, and CI/CD outcomes before and after rollout.

Core Features & Use Cases

  • Pre-flight safeguards: Runs TypeScript typecheck and performs a cross-layer audit of field names to catch mismatches across APIs, plugins, and type definitions.
  • Deployment readiness checks: Verifies current Kuro status and waits if Kuro is mid-cycle to avoid conflicting perception/action loops.
  • Change delivery with verification: Commits and pushes changes, waits for GitHub Actions completion, then confirms Kuro health and status using explicit UTC-labeled timestamps.

Quick Start

Ask the agent: “Deploy Kuro with typecheck, cross-layer field audit, CI/CD monitoring, and post-deploy health verification.”

Frequently Asked Questions about deploy-kuro

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

FAQPage Schema
How do I automate safe TypeScript deployments with GitHub Actions and post-deploy health verification?

Safe TypeScript deployments require running pnpm typecheck, committing and pushing changes, monitoring GitHub Actions CI/CD, and validating service health and status endpoints with UTC-labeled timestamps to confirm successful rollout.

What is a cross-layer field audit in TypeScript and when do I need it for deployment?

A cross-layer field audit performs grep-based checks on changed .ts files to catch field name mismatches across API endpoints, plugins, and type definitions. You need it when deploying TypeScript changes where runtime behavior depends on consistent field names across layers.

How do I prevent deployment conflicts when Kuro is running a perception action loop?

To prevent deployment conflicts during an active perception action loop, check local Kuro status endpoints before deploying and wait if Kuro is mid-cycle. After CI/CD completes, sleep for perception settle time before running final health verification.

Does deploy-kuro require pnpm for TypeScript typecheck and CI/CD monitoring?

Yes, safe Kuro deployments require executing pnpm typecheck as a pre-flight safeguard before pushing changes. The workflow then monitors GitHub Actions CI/CD completion and validates post-deploy service health using explicit UTC-labeled timestamps.

What is the best way to verify service health after a CI/CD deployment?

The best way to verify service health after CI/CD is to wait for GitHub Actions completion, sleep for the required perception settle time, then verify /health and /status outputs using explicit UTC-labeled timestamps to confirm the service is running correctly.

Why does my TypeScript deployment fail runtime checks when field names match in type definitions but not APIs?

TypeScript deployments fail runtime checks when field names mismatch across API endpoints, plugins, and type definitions. Running a grep-based cross-layer field audit on changed .ts files before deployment catches these structural inconsistencies that typecheck alone misses.