Pilot Dev Team Assistants Setup
/install pilot-dev-team-assistants-setup
Dev Team Assistants Setup
Deploy 4 agents that automate the PR workflow: review, test, docs, and coordination.
Roles
| Role | Hostname | Skills | Purpose |
|---|---|---|---|
| reviewer | \x3Cprefix>-reviewer |
pilot-github-bridge, pilot-review, pilot-chat | Reviews PR diffs for quality |
| test-runner | \x3Cprefix>-test-runner |
pilot-github-bridge, pilot-task-router, pilot-audit-log | Runs test suites |
| doc-writer | \x3Cprefix>-doc-writer |
pilot-github-bridge, pilot-share, pilot-task-router | Generates docs |
| coordinator | \x3Cprefix>-coordinator |
pilot-github-bridge, pilot-task-chain, pilot-slack-bridge, pilot-broadcast | Orchestrates and summarizes |
Setup Procedure
Step 1: Ask the user which role and prefix.
Step 2: Install skills:
# reviewer:
clawhub install pilot-github-bridge pilot-review pilot-chat
# test-runner:
clawhub install pilot-github-bridge pilot-task-router pilot-audit-log
# doc-writer:
clawhub install pilot-github-bridge pilot-share pilot-task-router
# coordinator:
clawhub install pilot-github-bridge pilot-task-chain pilot-slack-bridge pilot-broadcast
Step 3: Set hostname and write manifest to ~/.pilot/setups/dev-team-assistants.json.
Step 4: Handshake with coordinator (all agents handshake the coordinator).
Manifest Templates Per Role
coordinator
{
"setup": "dev-team-assistants", "role": "coordinator", "role_name": "PR Coordinator",
"hostname": "\x3Cprefix>-coordinator",
"skills": {
"pilot-github-bridge": "Watch GitHub for new PRs, post unified summary comments.",
"pilot-task-chain": "Fan out review/test/doc tasks and collect results.",
"pilot-slack-bridge": "Post PR status updates to Slack.",
"pilot-broadcast": "Broadcast new PR notifications to all assistants."
},
"data_flows": [
{ "direction": "send", "peer": "\x3Cprefix>-reviewer", "port": 1002, "topic": "pr-review", "description": "PR details for review" },
{ "direction": "send", "peer": "\x3Cprefix>-test-runner", "port": 1002, "topic": "pr-test", "description": "PR details for testing" },
{ "direction": "send", "peer": "\x3Cprefix>-doc-writer", "port": 1002, "topic": "pr-docs", "description": "PR details for docs" },
{ "direction": "receive", "peer": "\x3Cprefix>-reviewer", "port": 1002, "topic": "review-result", "description": "Review findings" },
{ "direction": "receive", "peer": "\x3Cprefix>-test-runner", "port": 1002, "topic": "test-result", "description": "Test results" },
{ "direction": "receive", "peer": "\x3Cprefix>-doc-writer", "port": 1001, "topic": "docs-result", "description": "Generated docs" }
],
"handshakes_needed": ["\x3Cprefix>-reviewer", "\x3Cprefix>-test-runner", "\x3Cprefix>-doc-writer"]
}
reviewer
{
"setup": "dev-team-assistants", "role": "reviewer", "role_name": "Code Reviewer",
"hostname": "\x3Cprefix>-reviewer",
"skills": {
"pilot-github-bridge": "Fetch PR diffs from GitHub.",
"pilot-review": "Analyze code for quality, security, and style issues.",
"pilot-chat": "Discuss review findings with coordinator."
},
"data_flows": [
{ "direction": "receive", "peer": "\x3Cprefix>-coordinator", "port": 1002, "topic": "pr-review", "description": "PR details" },
{ "direction": "send", "peer": "\x3Cprefix>-coordinator", "port": 1002, "topic": "review-result", "description": "Review findings" }
],
"handshakes_needed": ["\x3Cprefix>-coordinator"]
}
Data Flows
coordinator → reviewer/test-runner/doc-writer: PR details (port 1002)reviewer/test-runner → coordinator: results (port 1002)doc-writer → coordinator: generated docs (port 1001)
Workflow Example
# On coordinator — fan out:
pilotctl --json task submit \x3Cprefix>-reviewer --task '{"pr":1234,"repo":"acme/api","action":"review"}'
pilotctl --json task submit \x3Cprefix>-test-runner --task '{"pr":1234,"action":"test","branch":"feature/auth"}'
# On reviewer — return:
pilotctl --json publish \x3Cprefix>-coordinator review-result '{"pr":1234,"issues":2,"approval":"changes_requested"}'
# On test-runner — return:
pilotctl --json publish \x3Cprefix>-coordinator test-result '{"pr":1234,"passed":89,"failed":0,"coverage":82}'
Dependencies
Requires pilot-protocol skill, pilotctl binary, clawhub binary, and a running daemon.
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install pilot-dev-team-assistants-setup - After installation, invoke the skill by name or use
/pilot-dev-team-assistants-setup - Provide required inputs per the skill's parameter spec and get structured output
What is Pilot Dev Team Assistants Setup?
Deploy a dev team assistant system with 4 agents. Use this skill when: 1. User wants to automate code review, testing, and docs for PRs 2. User is configurin... It is an AI Agent Skill for Claude Code / OpenClaw, with 73 downloads so far.
How do I install Pilot Dev Team Assistants Setup?
Run "/install pilot-dev-team-assistants-setup" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Pilot Dev Team Assistants Setup free?
Yes, Pilot Dev Team Assistants Setup is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Pilot Dev Team Assistants Setup support?
Pilot Dev Team Assistants Setup is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Pilot Dev Team Assistants Setup?
It is built and maintained by Calin Teodor (@teoslayer); the current version is v1.0.0.