Repository navigation
docs(agents): keep prose out of shell commands - #83
Conversation
An apostrophe in a bash -c heredoc ended the quoting and ran review text as shell code in a main checkout.
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Sentinel dependency audit — WARN · ✓ ok144 allow · 5 warn · 0 block · 0 error
▶ Run Sentinel · 149 packages audited · 2026-11-09T14:56:51.952Z · SBOM uploaded as a build artifact |
Review follow-up: covers gh api and $(...), exempts titles, and removes inline-body and heredoc examples from agent docs and skills.
Agent instructions now say that PR bodies, reviews, comments and commit messages go in a file passed by path, never inline in a shell command, heredoc or
bash -cstring.On 2026-11-09 an agent posted reviews with
bash -c '... <<"EOF" ... EOF'. The apostrophe in "that's" ended the quoting, the review text ran as shell code from the Engine main checkout, and a backticked test name containing> returnscreated a strayreturnsfile there.The same one-line rule lands in every Engine repository's agent instructions (COD2-7153).
Validation:
git diff --check. Documentation only; no code, contract, infrastructure or runtime surface changes.