amuru

Execute external processes from .NET using the TimeWarp.Amuru fluent API.

19|Updated Jul 9, 2025
One-click install
npx skills add https://github.com/TimeWarpEngineering/timewarp-amuru --skill amuru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: amuru
Source: https://github.com/TimeWarpEngineering/timewarp-amuru/tree/main/skills/amuru
Command: npx skills add https://github.com/TimeWarpEngineering/timewarp-amuru --skill amuru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Execute external processes from .NET safely and with a fluent API that avoids direct System.Diagnostics.Process.Start, improving reliability and testability.

Core Features & Use Cases

  • Fluent Shell.Builder API for deterministic process execution
  • Streamed and captured output with robust error handling
  • DotNet, Git, and JSON-RPC integrations for automation and tooling
  • Safe defaults and easy configuration to reduce risky shell calls

Quick Start

Start by creating a Shell.Builder for your executable and chaining options to RunAsync, CaptureAsync, or PassthroughAsync.

Frequently Asked Questions about amuru

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

FAQPage Schema
How do I execute external processes from .NET safely?

To execute external processes safely from .NET, use a fluent Shell.Builder API that avoids direct System.Diagnostics.Process.Start calls, providing deterministic execution, streaming output, and robust error handling for automation tasks.

What is a fluent API for shell automation in C#?

A fluent API for shell automation in C# uses a Shell.Builder interface to chain execution options like RunAsync, CaptureAsync, or PassthroughAsync, providing type-safe process execution with streamed output and robust error handling.

Can I automate DotNet and Git CLI commands from C# code?

Yes, you can automate DotNet and Git CLI commands from C# code using a fluent process execution API that supports these executables natively, ensuring reliable configuration and deterministic scripting for CI tasks.

Does fluent process execution work for CI tasks and scripting in .NET?

Fluent process execution works for CI tasks and scripting in .NET by targeting automation workflows with safe defaults, easy configuration, and robust error handling to reduce risky shell calls during pipeline execution.

How do I capture and stream output from a process in C#?

To capture and stream output from a process in C#, chain configuration options on a Shell.Builder instance and call CaptureAsync or PassthroughAsync, which handle streamed output and robust error handling during execution.

Why avoid direct System.Diagnostics.Process.Start for automation?

Avoid direct System.Diagnostics.Process.Start for automation because it lacks safe defaults and testability, whereas a fluent API provides type-safe configuration, deterministic execution, and structured error handling for external processes.