huashu-agent-swarm

Coordinate autonomous agents via Git worktrees, task locks, and a dashboard.

16|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/Marwan78888/Neuron-Cli --skill huashu-agent-swarm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: huashu-agent-swarm
Source: https://github.com/Marwan78888/Neuron-Cli/tree/main/scratch/huashu-skills-master/huashu-agent-swarm
Command: npx skills add https://github.com/Marwan78888/Neuron-Cli --skill huashu-agent-swarm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enables a swarm of autonomous agents to coordinate work using Git with no central master, suitable for large projects.

Core Features & Use Cases

  • Git-based coordination: Agents claim tasks via lock files, reference TASKS.md, and use per-agent worktrees to isolate changes.
  • Distributed task ownership: Each agent independently selects, executes, and commits tasks, with progress tracked via commit history and current_tasks locks.
  • Observability & collaboration: A dashboard and simple logs provide visibility into agent status, progress, and logs for debugging.

Quick Start

Initialize a swarm-enabled project with the provided setup scripts, then start the swarm and monitor via the dashboard.

Frequently Asked Questions about huashu-agent-swarm

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

FAQPage Schema
How do I coordinate multiple autonomous agents for parallel coding on a large repository?

You can coordinate multiple autonomous agents by using a Git-based, self-organizing swarm with per-agent worktrees. This setup isolates changes, uses task locks for clear ownership, and tracks progress through commit history for auditable parallel coding.

How does Git-based task management work for distributed agent swarms?

Git-based task management works by having agents independently select and execute tasks from TASKS.md. Agents claim work via current_tasks lock files, operate in isolated Git worktrees, and commit changes to ensure distributed coordination without central orchestration.

Can I use Git worktrees to isolate changes for parallel coding tasks?

Yes, you can use Git worktrees to isolate changes for parallel coding tasks. The swarm uses per-agent worktrees so each autonomous agent can independently develop, execute, and commit tasks without interfering with others.

What is the best way to monitor autonomous agent progress and status in a distributed swarm?

The best way to monitor autonomous agent progress is through a lightweight dashboard and simple logs. These tools provide visibility into agent status, progress tracking, and debugging logs for peer collaboration within the swarm.

Do I need a central orchestration master to run a multi-agent swarm for large projects?

No, you do not need a central master to run a multi-agent swarm. The system uses a self-organizing swarm where each agent independently selects and executes tasks, suitable for large projects requiring minimal central orchestration.

When should I avoid using a Git-based swarm for distributed task coordination?

You should avoid using a Git-based swarm if your large project requires strict central orchestration rather than distributed task ownership. The self-organizing swarm relies on minimal central control and independent agent execution via lock files and worktrees.