AGENTS.md still imports the workspace parent; split for external legibility #3

New issue

Closed

opened 2026-05-23 20:54:21 +00:00 by coilysiren · 1 comment

coilysiren commented

2026-05-23 20:54:21 +00:00

Owner

Originally filed by @coilysiren on 2026-05-11T19:33:21Z - https://github.com/coilysiren/galaxy-gen/issues/40

galaxy-gen/AGENTS.md starts with 'See ../AGENTS.md for workspace-level conventions' and ends with a Kai-specific 'Post-push follow-up (auto-schedule)' section that names coily / kai-server. External contributors don't have the workspace parent or those tools, so both ends of the file are illegible to them.

Proposed split:

Keep the project-specific middle of AGENTS.md (project layout, dev loop, conventions, key references, CI).
Stop importing ../AGENTS.md. Inline the small amount of workspace-level discipline that's actually load-bearing for editing galaxy-gen (writing voice, git workflow basics) instead of pulling a private parent.
Move the 'Post-push follow-up' auto-schedule section to a separate file gitignored or kept in coilyco-ai, since it is a Kai-specific automation directive, not a project rule.

Worth doing in a dedicated session - non-trivial because deciding what to inline vs drop touches the contributor-vs-author boundary.

_Originally filed by @coilysiren on 2026-05-11T19:33:21Z - [https://github.com/coilysiren/galaxy-gen/issues/40](https://github.com/coilysiren/galaxy-gen/issues/40)_ galaxy-gen/AGENTS.md starts with 'See `../AGENTS.md` for workspace-level conventions' and ends with a Kai-specific 'Post-push follow-up (auto-schedule)' section that names coily / kai-server. External contributors don't have the workspace parent or those tools, so both ends of the file are illegible to them. Proposed split: - Keep the project-specific middle of AGENTS.md (project layout, dev loop, conventions, key references, CI). - Stop importing `../AGENTS.md`. Inline the small amount of workspace-level discipline that's actually load-bearing for editing galaxy-gen (writing voice, git workflow basics) instead of pulling a private parent. - Move the 'Post-push follow-up' auto-schedule section to a separate file gitignored or kept in coilyco-ai, since it is a Kai-specific automation directive, not a project rule. Worth doing in a dedicated session - non-trivial because deciding what to inline vs drop touches the contributor-vs-author boundary.

coilysiren commented

2026-06-17 08:23:33 +00:00

Author

Owner

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: burndown-2026-06.

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: `burndown-2026-06`.

coilysiren

2026-06-17 08:23:33 +00:00

closed this issue
added the
burndown-2026-06
label

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

coilyco-gaming/galaxy-gen#3

No description provided.

Rows
Columns