skills.rest
ruah-dev
ruah-devOFFICIAL
Explore all skills by this author →
GitHub

ruah-orchestrator

Coordinate isolated Git worktrees and file-claim locking for parallel AI agents.

11|2|Updated Apr 5, 2026
Search Tags:#workflow#worktrees#orchestration#artifacts#task-management#file-locking#ruah
One-click install
npx skills add https://github.com/ruah-dev/ruah-orch --skill ruah-orchestrator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ruah-orchestrator
Source: https://github.com/ruah-dev/ruah-orch/tree/main/.claude/skills/ruah-orchestrator
Command: npx skills add https://github.com/ruah-dev/ruah-orch --skill ruah-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ruah prevents concurrent edit collisions when multiple AI agents or executors work on the same repository by giving each task an isolated workspace, tracking file claims, and producing durable artifacts for safe merges.

Core Features & Use Cases

  • Isolated Workspaces: Creates Git worktrees per task so agents do not share a checkout and edits remain isolated.
  • Claim-Based File Locking: Tracks canonical claims for owned/shared/read-only access to prevent overlapping edits before execution.
  • Artifacts & Compatibility: Captures task artifacts, emits compatibility signals for dependency-ordered merges, and supports DAG workflows and governance gates.
  • Use Case: Run parallel AI agents to implement frontend and backend features in the same repo without merge conflicts, then validate and merge in dependency order.

Quick Start

Create and start an isolated task named auth that locks the src/auth/** files, run its executor to produce artifacts, then finalize and merge the task.

Frequently Asked Questions about ruah-orchestrator

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

FAQPage Schema
How do I prevent AI agents from causing merge conflicts in the same repository?▼

Git worktrees prevent concurrent edit collisions by giving each AI agent an isolated workspace, ensuring parallel edits remain separated until a safe merge. This stops overlapping edits before execution.

What is the best way to run parallel code edits without overwriting shared files?▼

Claim-based file locking prevents parallel code edits from overwriting shared files by tracking canonical claims for owned, shared, and read-only access across multiple agents.

How do I orchestrate dependency-ordered merges for parallel task branches?▼

Orchestrate dependency-ordered merges by capturing durable task artifacts and emitting compatibility signals. This supports DAG-based workflows and governance gates to sequence merges safely across parallel branches.

Can I use Git worktrees to isolate automated executor tasks in a DAG workflow?▼

Yes, Git worktrees isolate automated executor tasks in a DAG workflow. The system manages worktrees, file-claim locking, and structured JSON output to coordinate concurrent executors safely.

Do I need a specific Git setup to track file claims for isolated workspaces?▼

A software development repository supporting Git worktrees is required to track file claims for isolated workspaces. The system applies environment variables and structured JSON output to manage executor claims.

Related Skills

Explore More Software Engineering Skills→
bluefishsbluefishs

using-git-worktrees

Create isolated Git worktrees for feature branches with safety checks.

Community
Intermediate
cryborg1211cryborg1211

vc:merge-worktree

Merge a git worktree branch into the main checkout and prune it.

Community
Intermediate
maplin-comaplin-co

beads

Coordinate multi-agent tasks across sessions with file locking and dependencies.

Official
Advanced
CuriousLearnerCuriousLearner
27

conflict-resolver

Analyze Git merge conflict types and propose automated or manual resolution strategies.

Community
Advanced