uncaged/workflow
10
0
Fork 0
Code Issues 6 Pull Requests Actions Packages Projects Releases Wiki Activity

Phase 2 Testing: developer role + submitter role + solve-issue refactor #59

New Issue
Closed
opened 2026-05-07 13:39:36 +00:00 by xiaoju · 0 comments
xiaoju commented 2026-05-07 13:39:36 +00:00
Owner
Copy Link
Copy Source

验证目标

新建 developer role（extractMode: react，用 workflowAsAgent）和 submitter role。改造 solve-issue 为父 workflow：preparer → developer → submitter。

测试步骤

  • Step 1: developer role 存在

    bun run build

    预期： developer role 定义存在，extractMode: "react"，schema 包含 branch/commitSha/filesChanged/summary。agent 使用 workflowAsAgent("develop")。

  • Step 2: submitter role 存在

    bun run build

    预期： packages/workflow-role-submitter/ 存在，导出 submitterRole。systemPrompt 指导 agent 读 preparer 输出获取 repo 信息，push branch，创建 PR。schema: { status: "submitted" | "failed", prUrl: string | null, error: string | null }。

  • Step 3: solve-issue 改为 3-role 父 workflow

    bun test --filter "solve-issue"

    预期： solve-issue roles 为 preparer + developer + submitter。moderator：preparer → developer → submitter → END。不再直接依赖 planner/coder/reviewer/committer。

  • Step 4: solve-issue moderator 路由

    bun test --filter "solve-issue"

    预期：

    • 初始 → preparer
    • preparer → developer
    • developer → submitter
    • submitter submitted → END
    • submitter failed（可重试）→ submitter（如果 maxRounds 允许）

  • Step 5: 全量测试通过

    bun test && bun run build && bun run check

验证完成标准

✅ developer role extractMode: react
✅ submitter role push + PR
✅ solve-issue 为 3-role 父 workflow
✅ 全绿

Refs #55

## 验证目标 新建 developer role（extractMode: react，用 workflowAsAgent）和 submitter role。改造 solve-issue 为父 workflow：preparer → developer → submitter。 ## 测试步骤 - [ ] **Step 1: developer role 存在** ```bash bun run build ``` **预期：** developer role 定义存在，extractMode: "react"，schema 包含 branch/commitSha/filesChanged/summary。agent 使用 workflowAsAgent("develop")。 - [ ] **Step 2: submitter role 存在** ```bash bun run build ``` **预期：** `packages/workflow-role-submitter/` 存在，导出 submitterRole。systemPrompt 指导 agent 读 preparer 输出获取 repo 信息，push branch，创建 PR。schema: `{ status: "submitted" | "failed", prUrl: string | null, error: string | null }`。 - [ ] **Step 3: solve-issue 改为 3-role 父 workflow** ```bash bun test --filter "solve-issue" ``` **预期：** solve-issue roles 为 preparer + developer + submitter。moderator：preparer → developer → submitter → END。不再直接依赖 planner/coder/reviewer/committer。 - [ ] **Step 4: solve-issue moderator 路由** ```bash bun test --filter "solve-issue" ``` **预期：** - 初始 → preparer - preparer → developer - developer → submitter - submitter submitted → END - submitter failed（可重试）→ submitter（如果 maxRounds 允许） - [ ] **Step 5: 全量测试通过** ```bash bun test && bun run build && bun run check ``` ## 验证完成标准 ✅ developer role extractMode: react ✅ submitter role push + PR ✅ solve-issue 为 3-role 父 workflow ✅ 全绿 Refs #55
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
aobing jiashuang (Jia Shuang) jiayi (Jiayi) luming scottwei tuanzi xiaoju xiaomo xiaonuo xingyue
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: uncaged/workflow#59
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?