[codex] Document real-newline moon run snippets - #63
Merged
Conversation
bobzhang
marked this pull request as ready for review
July 5, 2026 13:49
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Document the safe pattern for multi-line
moon run -esnippets that need imports.Why
Shell snippets written as single-quoted strings with literal
\npass backslash characters to MoonBit instead of real line breaks. That makes inline imports fail in a way that looks like a MoonBit parsing/import issue rather than a shell quoting issue.Validation
SKILL.mddiff for scope and Markdown placement.moon run --target native -e "$(cat <<'EOF' ... EOF)"pattern successfully.quick_validate.pyagainst the skill using a temporary Python virtualenv with PyYAML installed:Skill is valid!.