Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

session: plan-born task worker briefs omit standing project orders

未关闭
#1,549 2 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@santoshkumarradha 已经在做这个了。

开始于 2026年9月27日。

  • #1598 来自 @santoshkumarradha —— 已关闭,未合并
  • #1604 来自 @santoshkumarradha —— 已关闭,未合并

评估

难度
3/5
预计耗时
1-2 天
新手友好度
78/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
go
领域
cli, devtools

调研方向

Start in internal/session/task_brief.go:225-300 and compare plan-born worker message composition with TaskGraph.briefLocked, which appends standing orders to node.brief. Reproduce with a plan containing a project standing order and inspect the worker prompt journal at .codeaf/v3/.../transcript.jsonl. Done means every applicable rule appears in prompts for workers created directly and through plans.

由索引模型根据 Issue 内容生成。

描述

area:session bug sev:critical
Summary

Standing project orders appended to node.brief are never included in worker prompt generation for tasks created from execution plans.

Observed Behavior

When a task is spawned via a plan, active standing orders (<standing> rules) defined for the project are missing from the system prompt given to the task worker, leading workers to violate project constraints.

Expected Behavior

Every delegated task worker must inherit all applicable standing orders for the target repository/project regardless of whether it was spawned directly or via a multi-step plan.

Reproduction Steps
  1. Add a standing order to a project (e.g. strict coding style or git branch constraints).
  2. Propose and approve a multi-step task that generates a plan graph.
  3. Inspect the worker prompt journal in .codeaf/v3/.../transcript.jsonl.
  4. Notice that <standing> orders are absent from the worker's brief.
Root Cause / Location

TaskGraph.briefLocked correctly appends standing orders to node.brief, but plan-born worker message composition in internal/session/task_brief.go:225-300 builds the prompt independently from plan template data and skips the appended standing rules.

—
Drafted with CodeAF · reviewed and owned by the author

主要语言
Go
星标
115
派生
14
平均合并
12 小时 30 分钟
30 天内合并 PR
323

环境准备

我们还没有检查这个项目的环境配置文件。先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

Agent-Field/CodeAF 的其他 Issue

查看 Agent-Field/CodeAF 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。