Zing 论坛

正文

Keel:将编码代理转化为工作负责人的多代理工作流框架

Keel是一个项目无关的多代理工作流骨架,能够将GitHub Issue从待办事项驱动至合并完成,实现从需求理解、分支创建、代码实现、CI等待、代码审查、测试验证到安全合并的端到端自动化。

keel多代理工作流GitHub自动化代码审查合并策略CI/CDLangGraphRAG
发布时间 2026/06/09 22:45最近活动 2026/06/09 22:53预计阅读 4 分钟
Keel:将编码代理转化为工作负责人的多代理工作流框架
1

章节 01

Keel: A Multi-Agent Workflow Framework for End-to-End Issue-to-Merge Automation

Keel is a project-agnostic multi-agent workflow backbone that automates the full lifecycle from GitHub Issue creation to PR merge—covering requirement understanding, branch creation, code implementation, CI waiting, code review, test validation, and secure merging. It fills gaps in existing tools by integrating coding agents, review tools, quality gates, and merge strategies into a unified work ownership framework.

2

章节 02

Background & Motivation for Keel

Existing coding agents (OpenHands, SWE-agent, Devin) stop at PR creation; PR review tools (CodeRabbit, PR-Agent) focus on existing PRs; merge queue tools (GitHub Merge Queue, Mergify) handle post-test merging. None cover the complete issue-to-merge lifecycle. Keel was built to bridge this gap as a unified workflow backbone.

3

章节 03

Core Architecture & 13-Step Workflow

Keel uses a 3-layer design: Layer1 (fixed keel-core backbone), Layer2 (project-specific config via project.yaml), Layer3 (add-only extensions). Its 13-step workflow includes key stages: implement (coding agent works), classify (risk grading), review (multi-agent via ai-jury), merge (security strategies like time zone locks), and capture (learning沉淀).

4

章节 04

Keel vs. Existing Tools

Keel complements rather than replaces existing tools:

  • Adds lifecycle management beyond PR creation for coding agents.
  • Extends PR review tools with implementation loops and merge strategies.
  • Provides issue ownership (pre-PR) for merge queue tools. It acts as a work ownership skeleton integrating these tools into a unified lifecycle.
5

章节 05

Installation, Commands & Quality Assurance

Installation: pip install keel-workflow (Python ≥3.11). Key commands: setup (project config), validate (config check), plan (workflow preview), ship (flagship command). Keel uses dogfooding (self-development via its own workflow) and maintains 100% test coverage for core packages.

6

章节 06

Real-World Application Scenarios

  1. Automated Issue Handling: End-to-end processing from issue creation to merge without manual intervention.
  2. Nightly Regression Testing: overnight command runs tests, checks dependencies, and creates issues for problems.
  3. Multi-agent Code Review: Integrates ai-jury to run multiple agents for comprehensive code reviews.
7

章节 07

Summary & Future Vision

Keel v1 focuses on single-agent work ownership. Long-term vision: Autonomous software teams (multiple agents under human supervision). It frees developers from routine tasks to focus on human-judgment work (product tradeoffs, approvals). Keel is key infrastructure connecting human intent and machine execution in software engineering automation.