aspire-orchestration

Manage Aspire AppHost lifecycle and recover from file locks, port conflicts, and orphaned processes.

Updated May 5, 2026
One-click install
npx skills add https://github.com/Movchanets/Microservices_Learning --skill aspire-orchestration-movchanets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aspire-orchestration
Source: https://github.com/Movchanets/Microservices_Learning/tree/main/.agents/skills/aspire-orchestration
Command: npx skills add https://github.com/Movchanets/Microservices_Learning --skill aspire-orchestration-movchanets

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents fragile Aspire workflows by managing AppHost startup, shutdown, readiness checks, and recovery from file locks, port conflicts, and orphaned processes.

Core Features & Use Cases

  • Lifecycle control: Start, stop, wait for, and inspect Aspire apps without using unsafe generic .NET commands.
  • Recovery guidance: Resolve build locks, blocked ports, and stuck resources with the correct Aspire CLI sequence.
  • Agent-safe operations: Use non-interactive, background-friendly commands for automated workflows and clean cleanup.
  • Use case: An AI assistant can safely bring up a distributed Aspire solution, wait for a service to be ready, diagnose a failed resource, and shut everything down when finished.

Quick Start

Ask the skill to start the Aspire app, wait for the target resource to become ready, and stop the environment when the task is complete.

Frequently Asked Questions about aspire-orchestration

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

FAQPage Schema
How do I fix Aspire port conflicts and file locks during local development?

Aspire port conflicts and file locks are resolved by running the correct CLI recovery sequence to clear orphaned processes and blocked ports, preventing locked builds and lingering resources during local development.

What is the safest way to manage the Aspire AppHost lifecycle for automated workflows?

Managing the Aspire AppHost lifecycle safely requires non-interactive, background-friendly CLI commands for startup, readiness checks, and shutdown, preventing fragile workflows and ensuring clean cleanup in automated environments.

How do I wait for a specific Aspire resource to become ready before running tests?

To wait for an Aspire resource to become ready, use JSON-formatted status checks to verify resource readiness, allowing you to proceed with tests only when the target service is fully operational and responsive.

Can I inspect and diagnose failed Aspire resources without using generic .NET commands?

Yes, you can inspect and diagnose failed Aspire resources using resource-scoped operations via Aspire CLI commands, avoiding unsafe generic .NET commands and providing targeted recovery guidance for stuck resources.

Why does my Aspire AppHost leave orphaned processes after I stop it?

Aspire AppHost leaves orphaned processes when standard shutdown methods fail to clear lingering resources, requiring a non-interactive stop sequence to ensure all background processes are properly terminated and cleaned up.