From 64d6c90284d77cb5bc7f529b9179eb84bbf7cee4 Mon Sep 17 00:00:00 2001 From: Oleks Date: Thu, 30 Jul 2026 19:24:54 +0300 Subject: [PATCH] Fix nested code-fence collision the pre-push formatter introduced The previous commit nested a triple-backtick example fence inside a triple-backtick pseudocode block; the repo's markdown auto-formatter treated the inner ``` as closing the outer block and reindented/moved the "for action == comment" case out of the Agent(...) call. Use ~~~ for the outer fence so the real triple-backtick example nests without collision. --- skills/offload-audit/SKILL.md | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/skills/offload-audit/SKILL.md b/skills/offload-audit/SKILL.md index 5091cb5..1440d4b 100644 --- a/skills/offload-audit/SKILL.md +++ b/skills/offload-audit/SKILL.md @@ -272,7 +272,7 @@ is read as markdown — `issuer-agent` can only paste a line byte-for-byte if it was actually shown one, not markdown that silently ate it. A fenced block (` ``` `) forces the body to be read and relayed as literal text. -```text +~~~text Agent(subagent_type="anxious:issuer-agent", prompt=...) # for action == "file" "File this on . It is an inference-arbitrage audit finding. @@ -284,7 +284,6 @@ Agent(subagent_type="anxious:issuer-agent", prompt=...) by design, so you will not visually see it in the rendered issue — that is expected, do not treat it as accidental syntax to strip: ``` - ``` Labels: 'token-offload' is required — create it on this repo if absent @@ -294,19 +293,17 @@ Agent(subagent_type="anxious:issuer-agent", prompt=...) domain/agents, activity/automate. Return the issue reference in full owner/repo#num form." -# for action == "comment" - + # for action == "comment" "Add this comment to , an existing inference-arbitrage finding being re-measured. Do not open a new issue. Copy the fenced block below byte-for-byte as the comment body — do not retype or reformat it, the first line is an invisible-by-design HTML-comment idempotency marker (see the 'file' case above for why). If the issue is closed, use your judgement about reopening; the audit does not require it. - ``` ```" -``` +~~~ `issuer` owns repo, final title, labels beyond `token-offload`, and milestone. You own the body.