Sembr reformat
Reformat prose using Semantic Line Breaks (SemBr) from https://sembr.org while preserving rendered output and meaning. Use when asked to reflow plain text or compatible markup (Markdown, AsciiDoc, reStructuredText, LaTeX, Org, MediaWiki) into semantic one-thought-per-line formatting, or when improving prose diffs and editorial readability.From its SKILL.md
npx -y skills add sembr/skills --skill sembr-reformatAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 11 stars11 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.0 KB, as published. Nobody here has run it
Reformat With SemBr
Apply Semantic Line Breaks to prose without changing what readers see. Preserve wording, punctuation, and intent.
Reformat Workflow
- Identify prose regions that support soft-wrapped lines.
- Skip regions where line breaks are syntactically significant:
- fenced code blocks and indented code blocks
- tables
- YAML frontmatter
- URLs or markup tokens that must stay contiguous
- Rewrite only line wrapping, not content.
- Keep paragraphs and list structures intact.
- Return full rewritten text unless asked for a targeted excerpt.
SemBr Rules
Apply these rules in order:
- Break after every sentence ending in
.,!, or?. - Prefer a break after independent clauses ending in
,,;,:, or—. - Optionally break after dependent clauses when it clarifies structure.
- Insert a break before an enumerated or itemized list.
- Optionally add breaks between list items to group related items.
- Never break inside a hyphenated word.
- Allow breaks around hyperlinks and before inline markup when helpful.
- Target 80 columns when possible; allow longer lines for URLs, code spans, or unavoidable markup.
Quality Checks
Before returning output, verify:
- Rendering-equivalence: no hard-break syntax added accidentally.
- Meaning-equivalence: no word changes or punctuation edits.
- Structure-equivalence: headings, lists, and block boundaries unchanged.
- Diff-friendliness: edits are mostly line-wrap changes.
Output Style
Use minimal explanation. Return reformatted text directly. If any segment cannot be safely reformatted, leave it unchanged and add a one-line note.