In-app coordinator/Ralph never reads .squad/ralph-instructions.md; only `squad watch --execute` does

未關閉 適合新手
#2,233 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
2/5
預估耗時
1-3 小時
新手友好度
78/100
Issue 類型
缺陷
描述清晰度
描述清楚
活躍度
活躍
技術堆疊
github, typescript

研究方向

閱讀 .github/agents/squad.agent.md 和 .squad/templates/ralph-reference.md,然後將其中的指示與 squad watch --execute 所描述的行為進行比較。更新 Ralph 派送指示,使其在 .squad/ralph-instructions.md 存在時載入該檔案,並修正參考檔案中的自我參照。當應用程式內的派送路徑遵循使用者自有的指示,且參照鏈指向預期檔案時,即為完成。

由索引模型根據 Issue 內容生成。

描述

wave:2-soon

Problem

.squad/ralph-instructions.md is the user-owned file for Ralph's repo rules. Its own header says squad init creates it and squad upgrade never overwrites it. But only squad watch --execute tells the spawned session to read it.

The in-app path never mentions the file. "Ralph, go" and coordinator-driven issue dispatch run from .github/agents/squad.agent.md (coordinator v1.0.1) and its on-demand .squad/templates/ralph-reference.md, and neither references .squad/ralph-instructions.md. So any rule a user writes there is skipped whenever the coordinator, rather than watch --execute, dispatches issue work.

Observed with squad-cli 1.0.1 on Windows:

  • The repo's ralph-instructions.md defines a multi-host claim protocol: assign the issue, comment "Claimed by ", and run an election over the issue timeline.
  • An in-app coordinator session dispatched about 10 issue sessions without claiming any of them.
  • Two issues were worked twice by the same coordinator across context windows, which a claim check would have prevented.
  • Other rules in that file are skipped too, including host concurrency limits and the round-report format.

.squad/templates/ralph-reference.md line 11 also points to itself ("Read .squad/templates/ralph-reference.md…"), so the reference chain ends there.

Expected

Every Ralph/coordinator work-dispatch path loads .squad/ralph-instructions.md when it exists, with the same precedence watch --execute gives it. That way the user-owned rules apply no matter how work is dispatched.

Suggested fix

  • In squad.agent.md, in the Ralph section and before any issue dispatch: "If {TEAM_ROOT}/.squad/ralph-instructions.md exists, read it and follow it before selecting or dispatching issue work."
  • Fix the self-reference in templates/ralph-reference.md.
  • Optionally, have the coordinator load it once per session alongside team.md/routing.md.

Workaround

Add a pointer in .github/copilot-instructions.md, which squad upgrade does not manage.

Related: #1314 (documenting the escape hatch).

主要語言
TypeScript
星號
3.4k
分支
516
平均合併
1 天 15 小時
30 天內合併 PR
116

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

github/squad 的其他 Issue

查看 github/squad 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。