skills.rest
Zeliper
ZeliperCOMMUNITY
Explore all skills by this author →
GitHub

spawn-orchestration-update

Spawn orchestration-update-agent updates and report COMPLETED, FAILED, or DRY_RUN outcomes.

Updated Dec 25, 2025
Search Tags:#automation#devops#versioning#orchestration#update#submodules
One-click install
npx skills add https://github.com/Zeliper/z-coder --skill spawn-orchestration-update
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spawn-orchestration-update
Source: https://github.com/Zeliper/z-coder/tree/main/.claude/skills/spawn-orchestration-update
Command: npx skills add https://github.com/Zeliper/z-coder --skill spawn-orchestration-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a guided process to perform /orchestration-update operations using the orchestration-update-agent, handling version selection, dry-run previews, and forced updates to keep submodules current with minimal risk.

Core Features & Use Cases

  • Command parsing: Extract options like --version, --dry-run, and --force from user input.
  • Spawn agent: Use the orchestration-update-agent via Task tool to perform updates in background.
  • Status reporting: Report COMPLETED, FAILED, or DRY_RUN with details and affected files.

Quick Start

Run /orchestration-update with a chosen option (e.g., --version latest or --dry-run) and let the orchestration-update-agent apply the changes.

Frequently Asked Questions about spawn-orchestration-update

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

FAQPage Schema
How do I automate orchestration updates with submodule syncing?▼

Orchestration updates automate keeping submodules current by spawning the orchestration-update-agent through the /orchestration-update command with options like --version, --dry-run, and --force. The agent applies changes in the background and reports completion status with affected file summaries.

What does a dry-run preview show before applying orchestration updates?▼

A dry-run preview executes the orchestration-update-agent without committing changes, displaying which files and submodules would be affected and what version updates would occur. This lets you verify changes before forcing a live update.

Can I update to a specific version when syncing orchestration submodules?▼

Yes, the orchestration-update-agent accepts a --version option to target a specific version during updates. You can specify --version latest or a particular version number to control which orchestration state the submodules sync to.

How do I handle failed orchestration updates and see error details?▼

Failed orchestration updates report a FAILED status with a summary of errors encountered. The agent logs what went wrong, allowing you to review the issue and retry with corrected parameters or use --force to override constraints if needed.

What happens when I force an orchestration update without dry-run verification?▼

Forcing an orchestration update with --force bypasses safeguards and applies changes immediately without a preview. Use this only after confirming changes via --dry-run first, as forced updates commit submodule versions directly without rollback options.

Related Skills

Explore More Software Engineering Skills→
benjaminshafiibenjaminshafii
10

sync-modules

Synchronize control-center master with upstream changes and update submodule pointers safely.

Community
Intermediate
sunholo-datasunholo-data
33

AILANG Release Manager

Automates end-to-end AILANG release management including pre-release checks, version bumps, changelog updates, git tagging, CI/CD verification, and release broadcasting.

Official
Intermediate
YoraexeYoraexe

trigger-dev

Orchestrate durable background jobs with Trigger.dev in TypeScript projects.

Community
Advanced
different-aidifferent-ai
63

sync-submodules

Synchronize Git submodules to pinned commits with optional stashing.

Official
Intermediate