<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Jonghun Yu</title>
    <description>The latest articles on DEV Community by Jonghun Yu (@jonghunyu).</description>
    <link>https://dev.to/jonghunyu</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4129015%2F452ff846-679a-4a9f-9345-48dc60226ccb.jpg</url>
      <title>DEV Community: Jonghun Yu</title>
      <link>https://dev.to/jonghunyu</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/jonghunyu"/>
    <language>en</language>
    <item>
      <title>I built Texio so coding agents can edit one Markdown section safely</title>
      <dc:creator>Jonghun Yu</dc:creator>
      <pubDate>Thu, 17 Sep 2026 04:10:19 +0000</pubDate>
      <link>https://dev.to/jonghunyu/i-built-texio-so-coding-agents-can-edit-one-markdown-section-safely-2n61</link>
      <guid>https://dev.to/jonghunyu/i-built-texio-so-coding-agents-can-edit-one-markdown-section-safely-2n61</guid>
      <description>&lt;p&gt;Coding agents often need to change one section in a README. The usual shortcuts—regex replacement or regenerating the whole file—can silently cross a structural boundary.&lt;/p&gt;

&lt;p&gt;I built &lt;a href="https://github.com/Allra-Fintech/texio" rel="noopener noreferrer"&gt;Texio&lt;/a&gt;, an MIT-licensed Rust CLI that gives agents a smaller, fail-closed interface for Markdown: list real headings, inspect one section, preview one replacement, then apply it explicitly.&lt;/p&gt;

&lt;p&gt;Here is a small failure case. The second heading-shaped line is only example text inside a fence:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight markdown"&gt;&lt;code&gt;&lt;span class="gh"&gt;# Demo&lt;/span&gt;

&lt;span class="gu"&gt;## Installation&lt;/span&gt;
old command

&lt;span class="p"&gt;```&lt;/span&gt;&lt;span class="nl"&gt;md
&lt;/span&gt;&lt;span class="gu"&gt;## Installation&lt;/span&gt;
example only
&lt;span class="p"&gt;```&lt;/span&gt;

&lt;span class="gu"&gt;## Usage&lt;/span&gt;
keep this
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A text regex can mistake the fenced line for a section boundary. Texio parses the document structure instead:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;cargo &lt;span class="nb"&gt;install &lt;/span&gt;texio-cli &lt;span class="nt"&gt;--version&lt;/span&gt; 0.1.2 &lt;span class="nt"&gt;--locked&lt;/span&gt;
texio headings demo.md &lt;span class="nt"&gt;--json&lt;/span&gt;
texio replace demo.md &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--section&lt;/span&gt; Installation &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--text&lt;/span&gt; &lt;span class="s1"&gt;'cargo install texio-cli --locked'&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--dry-run&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The dry run prints a unified diff and leaves the file unchanged. Replace &lt;code&gt;--dry-run&lt;/code&gt; with &lt;code&gt;--write&lt;/code&gt; only after reviewing that diff. If &lt;code&gt;Installation&lt;/code&gt; is missing or appears more than once as a real heading, Texio refuses to write instead of guessing.&lt;/p&gt;

&lt;p&gt;I also packaged this workflow as an &lt;a href="https://github.com/Allra-Fintech/texio/tree/main/skills/texio-markdown" rel="noopener noreferrer"&gt;Agent Skill&lt;/a&gt; for Codex, Claude Code, and compatible clients. The instructions make agents inspect headings, preview the exact edit, write it, and check the repository diff:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npx &lt;span class="nt"&gt;--yes&lt;/span&gt; skills@1.5.26 add &lt;span class="se"&gt;\&lt;/span&gt;
  https://github.com/Allra-Fintech/texio/tree/2141d66531ad10a748e11c566428fba3e80c7e4e/skills/texio-markdown &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--skill&lt;/span&gt; texio-markdown
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The checked-in &lt;a href="https://github.com/Allra-Fintech/texio/blob/main/launch/evidence/benchmark-v0.1.2.json" rel="noopener noreferrer"&gt;four-fixture benchmark&lt;/a&gt; passed 4/4 cases with Texio, 3/4 with an idealized whole-file baseline, and 2/4 with the disclosed regex proxy. That is a small mechanics benchmark, not a claim about every Markdown document, model, or token bill.&lt;/p&gt;

&lt;p&gt;I maintain Texio. I would especially value examples of repository automation that currently rewrites a README or uses a multiline regex to replace one named section.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Disclosure: I wrote and verified the project claims, commands, and results. AI tools assisted with development and editing this article; the DEV disclosure tier is “AI-Assisted (Some AI).”&lt;/em&gt;&lt;/p&gt;

</description>
      <category>showdev</category>
      <category>rust</category>
      <category>ai</category>
      <category>agents</category>
    </item>
  </channel>
</rss>
