Menu
Deploy Kuro changes through CI/CD pipeline with pre-flight checks and post-deploy verification
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Personal AI Agent with Memory + Proactivity - Multi-instance support
Pre-edit coordination ritual for the shared mini-agent tree — checks Kuro's cycle state, current branch, and whether worktree isolation is needed before touching src/ or memory/. Use before editing src/ or memory/ in the mini-agent repo.
Verify that code/config changes are actually persisted (committed + pushed + PR), not left uncommitted on the volatile runtime/main checkout. Use before claiming any "套用/執行/完成" of a change, or when a task asked to apply changes.
Run all mini-agent health-check and janitor scripts in one pass and summarize the results. Use when the user wants a project health check or types /health-sweep.
Check Kuro's current status, health, and recent activity in one shot
| name | deploy-kuro |
| description | Deploy Kuro changes through CI/CD pipeline with pre-flight checks and post-deploy verification |
| user_invocable | true |
Standardized deployment flow: test → audit → commit → push → wait for settle → verify.
Pre-flight: Type check
cd $CLAUDE_PROJECT_DIR && pnpm typecheck
If errors, fix them before proceeding. Do NOT skip.
Pre-flight: Cross-layer field audit
For all changed .ts files, grep for field names used in API endpoints, plugins, and type definitions. Verify they match across layers. Check that HTML files reference HTTP URLs, not file:// paths.
Pre-flight: Check Kuro status
curl -sf http://localhost:3001/status
Note the current cycle count and loop state. If Kuro is mid-cycle, wait for it to finish.
Commit & Push Stage changed files, write a descriptive commit message, and push to main.
git add <specific-files> && git commit -m "<message>" && git push origin main
Wait for CI/CD Monitor the GitHub Actions workflow:
gh run list --limit 1 --json status,conclusion,databaseId
Wait until the run completes. If it fails, check logs with gh run view <id> --log-failed.
Wait for Kuro to settle (30s) After deployment, Kuro's perception stream will detect workspace changes and may trigger cycles. Wait 30 seconds for the reactive cascade to complete.
sleep 30 && curl -sf http://localhost:3001/status | jq '{loop: .loop.cycleCount, busy: .claude.busy, mode: .loop.mode}'
Post-deploy verification Confirm Kuro is healthy and the changes are functional:
curl -sf http://localhost:3001/health
curl -sf http://localhost:3001/status | jq .
All timestamps in verification output must be labeled as UTC explicitly.
Report Summarize: what was deployed, CI/CD result, Kuro health status (with UTC timestamps), and any issues encountered.