Skip to content

fix: escape pipes inside inline code in markdown tables#31

Merged
khaliqgant merged 1 commit into
mainfrom
fix/escape-pipes-in-tables
May 9, 2026
Merged

fix: escape pipes inside inline code in markdown tables#31
khaliqgant merged 1 commit into
mainfrom
fix/escape-pipes-in-tables

Conversation

@khaliqgant

Copy link
Copy Markdown
Member

Summary

Three table cells in skills/writing-agent-relay-workflows/SKILL.md had unescaped | characters inside backticked inline code (`bash | bash | bash`, `cmd1 | cmd2`).

GitHub-flavored Markdown parses | as a column delimiter even inside backticks, so those rows rendered with too many columns and the tables broke.

Fixed by escaping the pipes as \|:

  • L31 — Conversation vs Pipeline table (Pipeline row)
  • L982 — Interactive Team decision table (last row)
  • L1279 — Common Mistakes table (first row)

Flagged by CodeRabbit and Devin Review on AgentWorkforce/relay#829.

Test plan

  • Visual: open the file on GitHub and confirm all three tables render with the correct column count.

🤖 Generated with Claude Code

Three table cells in writing-agent-relay-workflows/SKILL.md had unescaped
`|` characters inside backticked inline code (`bash | bash | bash`,
`cmd1 | cmd2`). GitHub-flavored Markdown still parses pipes as column
delimiters even inside backticks, which broke the column counts on those
rows. Escape them as `\|`.

Flagged by CodeRabbit and Devin Review on AgentWorkforce/relay#829.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented May 9, 2026

Copy link
Copy Markdown

Review Change Stack

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 2524f644-a0e0-4e51-955b-3c5daf689cfa

📥 Commits

Reviewing files that changed from the base of the PR and between 5b53ada and d94b5cf.

📒 Files selected for processing (1)
  • skills/writing-agent-relay-workflows/SKILL.md

📝 Walkthrough

Walkthrough

Three inline code examples in the skills documentation now escape pipe characters with backslashes (bash \| bash \| bash and cmd1 \| cmd2) to prevent unintended Markdown table cell parsing. Changes occur in the pipeline shape comparison, interactive team guidance, and common mistakes sections.

Changes

Markdown Escaping Corrections

Layer / File(s) Summary
Pipe Character Escaping
skills/writing-agent-relay-workflows/SKILL.md
Three inline code examples escape pipes using backslash notation: pipeline shape comparison (line 31), interactive team vs one-shot DAG rule (line 982), and common mistakes table (line 1279).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A rabbit hops through markdown's field,
Where pipes were bare, now shields revealed,
With backslash guards in backticks tight,
The code examples now render right! ✨
Escape the chaos, keep the peace—
One bar at a time, concerns decrease.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/escape-pipes-in-tables

Comment @coderabbitai help to get the list of available commands and usage tips.

@khaliqgant khaliqgant merged commit c1bc425 into main May 9, 2026
0 of 2 checks passed
@khaliqgant khaliqgant deleted the fix/escape-pipes-in-tables branch May 9, 2026 09:27

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Open in Devin Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant