GitHub Comment Body-File Safety Problem Inline looks convenient, but shell parsing happens before GitHub CLI sees the text. If the body contains backticks, , code fences, or other shell-significant characters, the shell can: - execute unintended commands - strip or mangle content - turn file paths into failing shell commands - post broken comments This happened in live use when a GitHub comment included markdown code spans like and inline; the shell tried to execute those paths. Rule If the body contains any markdown/code formatting or dynamic content, use . Do not use inline . Safe pattern A…