gitea-coordinator
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseGitea Coordinator
Gitea协调器
Orchestrates multiple worker agents to implement groomed tasks from the backlog in Gitea repositories, handling task assignment, progress monitoring, merge coordination, and verification.
编排多个worker agent以处理Gitea仓库待办事项中已梳理好的任务,负责任务分配、进度监控、合并协调及验证工作。
Core Principle
核心原则
Coordinate, don't implement. The coordinator assigns tasks to workers, monitors their progress, coordinates merges, and verifies results. Workers execute the actual implementation via the skill.
gitea-workflow仅协调,不实现。 协调器将任务分配给工作者,监控其进度,协调合并操作并验证结果。工作者通过技能执行实际的任务实现工作。
gitea-workflowQuick Reference
快速参考
When to Use
使用场景
- Working with a Gitea-hosted repository
- Multiple ready tasks in the backlog need implementation
- You want autonomous batch execution of development work
- You need coordinated merges to avoid conflicts
- You want progress tracking across multiple tasks
- 操作Gitea托管的仓库
- 待办事项中有多个已就绪的任务需要实现
- 希望自主批量执行开发工作
- 需要协调合并操作以避免冲突
- 需要跟踪多个任务的进度
Invocation
调用方式
bash
/gitea-coordinator # Auto-discover and execute ready tasks
/gitea-coordinator TASK-001 TASK-002 # Execute specific tasks
/gitea-coordinator --dry-run # Preview execution plan only
/gitea-coordinator --parallel # Run workers in parallel
/gitea-coordinator --sequential # Run workers one at a time (default)bash
/gitea-coordinator # 自动发现并执行就绪任务
/gitea-coordinator TASK-001 TASK-002 # 执行指定任务
/gitea-coordinator --dry-run # 仅预览执行计划
/gitea-coordinator --parallel # 并行运行工作者
/gitea-coordinator --sequential # 依次运行工作者(默认)Flags
标志参数
| Flag | Description | Default |
|---|---|---|
| Execute tasks one at a time | Yes |
| Execute tasks concurrently | No |
| Maximum concurrent workers | 2 |
| Show plan without executing | No |
| Auto-continue at all checkpoints | Yes |
| Pause after each task completes | No |
| Show all worker updates | No |
| Show major milestones only | Yes |
| 标志 | 描述 | 默认值 |
|---|---|---|
| 依次执行任务 | 是 |
| 并发执行任务 | 否 |
| 最大并发工作者数量 | 2 |
| 仅显示计划不执行 | 否 |
| 在所有检查点自动继续 | 是 |
| 每个任务完成后暂停 | 否 |
| 显示所有工作者更新信息 | 否 |
| 仅显示主要里程碑 | 是 |
Workflow Phases
工作流阶段
Phase 1: Discovery
阶段1:发现
Read the backlog to find tasks ready for implementation.
Actions:
1. Read context/backlog/ for task files
2. Filter to status: ready
3. Parse task metadata (priority, size, dependencies)
4. Sort by priority (high → medium → low)
5. Present findings
Output: List of ready tasks with metadata读取待办事项以找到可实现的就绪任务。
操作步骤:
1. 读取context/backlog/目录下的任务文件
2. 筛选状态为:ready的任务
3. 解析任务元数据(优先级、规模、依赖关系)
4. 按优先级排序(高 → 中 → 低)
5. 展示发现结果
输出:包含元数据的就绪任务列表Phase 2: Planning
阶段2:规划
Create an execution plan based on task characteristics.
Actions:
1. Determine execution mode (sequential or parallel)
2. Check for task dependencies (A must complete before B)
3. Assign tasks to workers in priority order
4. Generate worker instructions
Output: Execution plan with task assignmentsCheckpoint: TASKS_DISCOVERED
- Display: Ready tasks and proposed execution plan
- Auto-continue: If --autonomous flag and tasks found
- Options: ,
continue,reorder,exclude [TASK-ID]stop
根据任务特性创建执行计划。
操作步骤:
1. 确定执行模式(依次或并行)
2. 检查任务依赖关系(任务A必须在任务B之前完成)
3. 按优先级顺序将任务分配给工作者
4. 生成工作者指令
输出:包含任务分配的执行计划检查点:TASKS_DISCOVERED
- 展示内容:就绪任务及建议的执行计划
- 自动继续:如果设置了--autonomous标志且找到任务
- 可选操作:(继续)、
continue(重新排序)、reorder(排除指定任务)、exclude [TASK-ID](停止)stop
Phase 3: Execution
阶段3:执行
Spawn and monitor worker agents.
For SEQUENTIAL mode:
for each task in queue:
1. Spawn worker with Task tool
2. Worker runs gitea-workflow for the task
3. Monitor progress via file system
4. When complete: proceed to merge phase
5. On failure: handle error, decide continue/stop
For PARALLEL mode:
1. Spawn workers up to max_workers
2. Monitor all workers concurrently
3. As workers complete: queue their PRs for merge
4. Spawn next worker if tasks remain
5. Continue until all tasks processedCheckpoint: WORKER_COMPLETE (per worker)
- Display: Worker summary, PR number, next action
- Auto-continue: If successful and --autonomous
- Options: ,
continue,retry,skipstop
生成并监控worker agent。
对于SEQUENTIAL(依次)模式:
针对队列中的每个任务:
1. 使用Task工具生成工作者
2. 工作者为该任务运行`gitea-workflow`
3. 通过文件系统监控进度
4. 完成后:进入合并阶段
5. 失败时:处理错误,决定继续/停止
对于PARALLEL(并行)模式:
1. 生成最多max_workers数量的工作者
2. 同时监控所有工作者
3. 工作者完成后:将其PR加入合并队列
4. 若还有任务未处理,生成下一个工作者
5. 持续直到所有任务处理完成检查点:WORKER_COMPLETE(每个工作者完成时)
- 展示内容:工作者摘要、PR编号、下一步操作
- 自动继续:如果任务成功且设置了--autonomous
- 可选操作:(继续)、
continue(重试)、retry(跳过)、skip(停止)stop
Phase 4: Merging
阶段4:合并
Execute merges sequentially to avoid conflicts.
Actions:
1. For each completed PR in merge queue:
a. git checkout main && git pull
b. Merge PR (via tea pulls merge or git merge)
c. Verify merge succeeded
d. Delete feature branch
2. If conflict: pause and alert user
Output: All PRs merged to main依次执行合并操作以避免冲突。
操作步骤:
1. 针对合并队列中的每个已完成PR:
a. git checkout main && git pull
b. 合并PR(通过tea pulls merge或git merge)
c. 验证合并成功
d. 删除功能分支
2. 若出现冲突:暂停并提醒用户
输出:所有PR已合并到main分支Phase 5: Verification
阶段5:验证
Verify system integrity after all merges.
Actions:
1. git checkout main && git pull --rebase
2. npm run build (verify build passes)
3. npm test (run full test suite)
4. Check for regressions
5. Generate verification report
Output: Verification status (PASSED/FAILED)Checkpoint: VERIFIED
- Display: Test results, build status
- Auto-continue: If all tests pass
- Options: ,
done,investigaterevert
所有合并完成后验证系统完整性。
操作步骤:
1. git checkout main && git pull --rebase
2. npm run build(验证构建通过)
3. npm test(运行完整测试套件)
4. 检查是否存在回归问题
5. 生成验证报告
输出:验证状态(PASSED/FAILED)检查点:VERIFIED
- 展示内容:测试结果、构建状态
- 自动继续:如果所有测试通过
- 可选操作:(完成)、
done(调查)、investigate(回滚)revert
Phase 6: Summary
阶段6:总结
Generate comprehensive completion report.
Output:
- Tasks completed with PR numbers and commits
- Metrics (workers spawned, PRs merged, tests added)
- Verification status
- Remaining backlog tasks生成全面的完成报告。
输出内容:
- 已完成的任务及其PR编号和提交记录
- 指标(生成的工作者数量、合并的PR数量、新增的测试用例)
- 验证状态
- 待办事项中剩余的任务Worker Protocol
工作者协议
Workers are spawned using Claude Code's Task tool and run for their assigned task.
gitea-workflow工作者通过Claude Code的Task工具生成,并为分配的任务运行。
gitea-workflowWorker Instruction Template
工作者指令模板
See templates/worker-instruction.md
Key requirements for workers:
- Run with autonomous mode
gitea-workflow - Write progress to
.coordinator/workers/{worker-id}/progress.json - Do NOT self-merge - signal ready-to-merge status instead
- Handle all gitea-workflow checkpoints automatically
查看templates/worker-instruction.md
工作者的关键要求:
- 以自主模式运行
gitea-workflow - 将进度写入
.coordinator/workers/{worker-id}/progress.json - 不得自行合并 - 而是发出ready-to-merge状态信号
- 自动处理所有gitea-workflow检查点
Progress Tracking
进度跟踪
Workers report progress via file system:
json
// .coordinator/workers/worker-1/progress.json
{
"worker_id": "worker-1",
"task_id": "TASK-006",
"status": "in_progress|completed|failed|ready-to-merge",
"phase": "implement|review|pr-prep|pr-complete",
"pr_number": null,
"branch": "task/TASK-006-description",
"last_update": "2026-01-20T10:15:00Z",
"milestones": [
{"phase": "implement", "timestamp": "..."},
{"phase": "review", "timestamp": "..."}
]
}工作者通过文件系统报告进度:
json
// .coordinator/workers/worker-1/progress.json
{
"worker_id": "worker-1",
"task_id": "TASK-006",
"status": "in_progress|completed|failed|ready-to-merge",
"phase": "implement|review|pr-prep|pr-complete",
"pr_number": null,
"branch": "task/TASK-006-description",
"last_update": "2026-01-20T10:15:00Z",
"milestones": [
{"phase": "implement", "timestamp": "..."},
{"phase": "review", "timestamp": "..."}
]
}State Tracking
状态跟踪
The coordinator maintains state in :
.coordinator/state.jsonjson
{
"session_id": "coord-2026-01-20-abc123",
"state": "EXECUTING",
"config": {
"execution_mode": "sequential",
"autonomy_level": "autonomous"
},
"tasks": {
"queued": ["TASK-008"],
"in_progress": ["TASK-007"],
"completed": ["TASK-006"],
"failed": []
},
"workers": [...],
"merge_queue": [],
"verification": null
}See references/state-tracking.md for details.
协调器在中维护状态:
.coordinator/state.jsonjson
{
"session_id": "coord-2026-01-20-abc123",
"state": "EXECUTING",
"config": {
"execution_mode": "sequential",
"autonomy_level": "autonomous"
},
"tasks": {
"queued": ["TASK-008"],
"in_progress": ["TASK-007"],
"completed": ["TASK-006"],
"failed": []
},
"workers": [...],
"merge_queue": [],
"verification": null
}详情查看references/state-tracking.md。
Failure Handling
故障处理
| Failure Type | Detection | Recovery |
|---|---|---|
| Worker fails | Progress shows | Offer retry, skip, or abort |
| Tests fail | npm test exits non-zero | Worker retries up to 2x |
| Merge conflict | git merge fails | Pause, alert user |
| Verification fails | Post-merge tests fail | Offer investigate or revert |
See references/failure-handling.md for details.
| 故障类型 | 检测方式 | 恢复方式 |
|---|---|---|
| 工作者失败 | 进度显示为 | 提供重试、跳过或终止选项 |
| 测试失败 | npm test返回非零退出码 | 工作者最多重试2次 |
| 合并冲突 | git merge失败 | 暂停并提醒用户 |
| 验证失败 | 合并后测试失败 | 提供调查或回滚选项 |
详情查看references/failure-handling.md。
Integration with gitea-workflow
与gitea-workflow的集成
The coordinator spawns workers that execute :
gitea-workflowgitea-coordinator (orchestrator)
│
├── Worker 1 → gitea-workflow --task TASK-006
├── Worker 2 → gitea-workflow --task TASK-007
└── Worker 3 → gitea-workflow --task TASK-008Key integration points:
- Workers run gitea-workflow in autonomous mode
- Coordinator handles merges (workers create PRs but don't merge)
- Progress synced via file system
- Coordinator runs verification after all merges
协调器生成的工作者会执行:
gitea-workflowgitea-coordinator(编排器)
│
├── Worker 1 → gitea-workflow --task TASK-006
├── Worker 2 → gitea-workflow --task TASK-007
└── Worker 3 → gitea-workflow --task TASK-008关键集成点:
- 工作者以自主模式运行gitea-workflow
- 协调器处理合并操作(工作者创建PR但不合并)
- 通过文件系统同步进度
- 所有合并完成后,协调器运行验证
Anti-Patterns
反模式
AP1: Parallel Merges
AP1:并行合并
Pattern: Merging multiple PRs simultaneously
Problem: Creates merge conflicts, corrupts main branch
Fix: Always merge sequentially, pull before each merge
模式:同时合并多个PR
问题:产生合并冲突,损坏main分支
修复方案:始终依次合并,每次合并前拉取最新代码
AP2: Worker Self-Merge
AP2:工作者自行合并
Pattern: Workers merge their own PRs
Problem: Race conditions, uncoordinated merges
Fix: Workers signal ready-to-merge, coordinator executes merges
模式:工作者合并自己创建的PR
问题:竞态条件,合并操作未协调
修复方案:工作者发出ready-to-merge信号,由协调器执行合并
AP3: No Verification
AP3:跳过验证
Pattern: Skipping post-merge verification
Problem: Regressions go undetected
Fix: Always run full test suite after merges complete
模式:跳过合并后的验证步骤
问题:回归问题未被发现
修复方案:合并完成后始终运行完整测试套件
Example Interaction
交互示例
User: /gitea-coordinator
Coordinator: Discovering ready tasks...
Found 2 ready tasks:
1. TASK-006 - Persistent Message Status (medium priority, medium size)
2. TASK-007 - Add Unit Tests (high priority, large size)
Execution Plan:
- Mode: sequential
- Order: TASK-006 → TASK-007
Proceed? [continue/reorder/stop]
User: continue
Coordinator: Starting TASK-006...
[Spawns Worker 1]
**Milestone**: TASK-006 - PR #123 created, CI passing
Coordinator: Merging PR #123...
**Milestone**: TASK-006 complete (commit abc123)
Coordinator: Starting TASK-007...
[Spawns Worker 2]
**Milestone**: TASK-007 - PR #124 created, CI passing
Coordinator: Merging PR #124...
**Milestone**: TASK-007 complete (commit def456)
Coordinator: Running verification...
- Build: PASSED
- Tests: 47/47 passing
- Coverage: 82%用户:/gitea-coordinator
协调器:正在发现就绪任务...
找到2个就绪任务:
1. TASK-006 - 持久化消息状态(中等优先级,中等规模)
2. TASK-007 - 添加单元测试(高优先级,大规模)
执行计划:
- 模式:依次执行
- 顺序:TASK-006 → TASK-007
是否继续? [continue/reorder/stop]
用户:continue
协调器:开始执行TASK-006...
[生成Worker 1]
**里程碑**:TASK-006 - PR #123已创建,CI通过
协调器:正在合并PR #123...
**里程碑**:TASK-006完成(提交abc123)
协调器:开始执行TASK-007...
[生成Worker 2]
**里程碑**:TASK-007 - PR #124已创建,CI通过
协调器:正在合并PR #124...
**里程碑**:TASK-007完成(提交def456)
协调器:正在运行验证...
- 构建:PASSED
- 测试:47/47通过
- 覆盖率:82%Summary
总结
Tasks completed: 2
- TASK-006: PR #123 merged (commit abc123)
- TASK-007: PR #124 merged (commit def456)
Verification: PASSED
---已完成任务:2个
- TASK-006:PR #123已合并(提交abc123)
- TASK-007:PR #124已合并(提交def456)
验证状态:PASSED
---Integration Graph
集成图
Inbound (From Other Skills)
入站(来自其他技能)
| Source Skill | Trigger | Action |
|---|---|---|
| requirements-elaboration | Tasks groomed | Coordinator can execute |
| gitea-agile | Backlog ready | Coordinator discovers tasks |
| 来源技能 | 触发条件 | 操作 |
|---|---|---|
| requirements-elaboration | 任务已梳理完成 | 协调器可执行任务 |
| gitea-agile | 待办事项已就绪 | 协调器发现任务 |
Outbound (To Other Skills)
出站(到其他技能)
| This Action | Triggers Skill | For |
|---|---|---|
| Spawn worker | gitea-workflow | Task implementation |
| Verification fails | research | Debug investigation |
| 本操作 | 触发技能 | 用途 |
|---|---|---|
| 生成工作者 | gitea-workflow | 任务实现 |
| 验证失败 | research | 调试调查 |
Complementary Skills
互补技能
| Skill | Relationship |
|---|---|
| gitea-workflow | Workers execute this skill |
| gitea-agile | Manages backlog this reads |
| 技能 | 关系 |
|---|---|
| gitea-workflow | 工作者执行该技能 |
| gitea-agile | 管理协调器读取的待办事项 |
Design Constraints
设计约束
- Requires Claude Code's Task tool for spawning workers
- Workers cannot directly communicate with each other
- File system used for progress coordination
- Sequential merges only (parallel merges disabled)
- Assumes context network backlog structure
- 需要Claude Code的Task工具来生成工作者
- 工作者之间无法直接通信
- 通过文件系统进行进度协调
- 仅支持依次合并(并行合并已禁用)
- 假设使用context network待办事项结构
What You Do NOT Do
不支持的操作
- Implement tasks directly (workers do this)
- Merge PRs in parallel (always sequential)
- Skip verification (always verify after merges)
- Continue after critical failures without user consent
- 直接实现任务(由工作者完成)
- 并行合并PR(始终依次合并)
- 跳过验证步骤(合并后始终验证)
- 未经用户同意的情况下在严重失败后继续执行