weiqingy commented on issue #894: URL: https://github.com/apache/flink-agents/issues/894#issuecomment-4988278448
Sounds good, @wenjin272 — the per-change-type files are the right call; they keep `code_review.md` a thin index while a type's detailed checklist only loads when an agent touches that kind of change. I'll open a first PR with the change-type matrix as an index in `code_review.md` plus one type — `runtime/` state & recovery — fully worked as the template, with its examples linked to the real review threads that caught them (#874, #880). Once the shape looks right we can fill in the remaining types one small PR each. I'll put the per-type files under `review-guides/` (happy to move them under `.github/` if you'd rather keep the root uncluttered). Separately, item 4 is up as #910 — a one-line `CLAUDE.md` importing `AGENTS.md` via `@AGENTS.md` rather than a symlink (a checked-in symlink degrades to a plain text file on Windows under `core.symlinks=false`). And I'll sequence module-scoped `AGENTS.md` (item 3) after this lands, since both rely on the same load-nearest-file-on-demand behaviour. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
