This is an automated email from the ASF dual-hosted git repository.
terrymanu pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/shardingsphere.git
The following commit(s) were added to refs/heads/master by this push:
new fffe6a3bec7 Refine review-pr Markdown output requirement (#39005)
fffe6a3bec7 is described below
commit fffe6a3bec751a8434f95cb8bc51e966b69fb1cc
Author: Liang Zhang <[email protected]>
AuthorDate: Sun Jul 5 15:56:46 2026 +0800
Refine review-pr Markdown output requirement (#39005)
Clarify that Formal Review Mode responses in Codex chat must be emitted as
exactly one fenced markdown block with no surrounding prose, and add a final
envelope self-check.
---
.codex/skills/review-pr/SKILL.md | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/.codex/skills/review-pr/SKILL.md b/.codex/skills/review-pr/SKILL.md
index 44f42cc2c88..2ac16853a6e 100644
--- a/.codex/skills/review-pr/SKILL.md
+++ b/.codex/skills/review-pr/SKILL.md
@@ -479,7 +479,8 @@ and contain exactly one bold `Review Result: ...` line
under `### Summary`.
Use stable English labels, repo-relative file references with line numbers,
public anchors, and sanitized verification summaries.
Do not wrap posted GitHub text in fences, blockquotes, XML/HTML, or
transcripts.
Do not include internal drafts, self-review notes, private context, local
absolute paths, temp paths, tokens, or raw long logs.
-When returning copy-ready text in Codex chat, wrap only the GitHub-facing body
in a fenced `markdown` block.
+In Codex chat, Formal Review Mode final output MUST be exactly one fenced
`markdown` block containing the entire GitHub-facing review body, with no prose
before or after the block.
+Before final output, verify the first non-empty line is ```markdown and the
last non-empty line is ```.
Use these required structures:
