crowi-orchestrate

Orchestrates worktree integration, spec grooming, code review, and security alert monitoring per tick.

1.1k|165|Updated Aug 18, 2014
One-click install
npx skills add https://github.com/crowi/crowi --skill crowi-orchestrate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crowi-orchestrate
Source: https://github.com/crowi/crowi/tree/main/.claude/skills/crowi-orchestrate
Command: npx skills add https://github.com/crowi/crowi --skill crowi-orchestrate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating parallel feature work across git worktrees, specs, reviews, and security alerts in the Crowi monorepo requires constant manual polling; this Skill automates that per-tick orchestration so nothing stalls or gets missed.

Core Features & Use Cases

  • Worktree integration watcher: Detects tasks marked READY_TO_INTEGRATE, verifies the signal against the actual branch HEAD, and hands off to the integrate-worktree flow.
  • Spec groomer: Validates implementation specs with a shared validator script and reports which are ready, which are missing elements, and which are deletion candidates.
  • Main-branch review watcher: Triggers a code review once meaningful non-merge commits accumulate directly on main.
  • Alert and stall detection: Reports new Dependabot security alerts, stalled worktrees, and new or updated flaky-test GitHub issues.
  • Use Case: Run it on a loop in the main session so that every tick it integrates one ready worktree, grooms specs, reviews accumulated main commits, and surfaces new Dependabot or flaky-test events without pushing or deleting anything autonomously.

Quick Start

Run the crowi-orchestrate skill on a loop in the main session to monitor worktrees, specs, reviews, and alerts each tick.

Frequently Asked Questions about crowi-orchestrate

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

FAQPage Schema
How do I automate git worktree integration in a monorepo?

Run this orchestration skill on a loop; each tick it scans task state files for READY_TO_INTEGRATE signals, verifies the worktree is clean and the recorded head SHA matches the branch HEAD, then invokes the integrate-worktree flow for one worktree per tick.

How to monitor Dependabot security alerts with the GitHub CLI?

The skill queries open Dependabot alerts via gh api repos/crowi/crowi/dependabot/alerts, diffs them against a stored list of known alert numbers, and reports only new advisories with severity, package, and first patched version. Fixes are delegated to a separate dependency skill.

Can this skill push commits or delete specs automatically?

No. It never pushes, never auto-deletes specs, never commits to a dirty main branch, and never bumps dependencies. Deletion candidates and fixes are reported as proposals that wait for explicit user approval.

What happens when a worktree stalls without a merge signal?

The stall watcher flags worktrees with commits ahead of main, no valid readyForMerge signal, and no commits for a threshold of days (3 by default, 14 for longLived tasks). It reports the stall only and does not interrupt the worktree session.

Does the orchestrator review worktree changes twice?

No. Worktree changes are already reviewed during the integrate flow, so the review lane only covers non-merge commits made directly on main, using first-parent log filtering to exclude merge commits and worktree history.

What are the limitations of the watch mode versus loop mode?

Watch mode uses a persistent bash monitor script that emits events with zero token cost, but its dedup state lasts only for the process lifetime and may re-fire once after restart. Loop mode polls every tick and remains the fallback where the watcher cannot run.