semantic-line-breaks

Apply semantic line breaks to prose after sentence-ending punctuation and before enumerated lists.

13|6|Updated Feb 23, 2013
One-click install
npx skills add https://github.com/abhinav/home --skill semantic-line-breaks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: semantic-line-breaks
Source: https://github.com/abhinav/home/tree/main/.claude/skills/semantic-line-breaks
Command: npx skills add https://github.com/abhinav/home --skill semantic-line-breaks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures all written prose—from code comments to commit messages and Markdown—is consistently formatted with semantic line breaks, drastically improving readability, diff clarity, and maintainability across all text-based content.

Core Features & Use Cases

  • Logical Line Breaking: Guides on breaking lines at natural, logical points (after sentences, clauses, list items) for optimal flow and comprehension.
  • Line Length Compliance: Provides clear guidelines for preferred and absolute line length limits across different contexts (e.g., commit messages, code comments, Markdown).
  • Enhanced Diff Readability: Improves the clarity of version control diffs by ensuring changes are isolated to specific logical units.
  • Use Case: When drafting a complex technical document, a detailed commit message, or multi-line code comments, this Skill automatically applies semantic line breaks, making the text easier to review, understand, and maintain.

Quick Start

BAD: all on one line

All human beings are born free and equal in dignity and rights. They are endowed with reason and conscience and should act towards one another in a spirit of brotherhood.

GOOD: with semantic line breaks

All human beings are born free and equal in dignity and rights. They are endowed with reason and conscience and should act towards one another in a spirit of brotherhood.

Frequently Asked Questions about semantic-line-breaks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do semantic line breaks improve readability in markdown and code comments?

Semantic line breaks split prose at logical points—after sentences, clauses, and before lists—rather than at arbitrary character limits. This breaks text into meaningful units, making code reviews, diffs, and long-form comments easier to scan and understand without sacrificing flow.

What's the best way to format commit messages for better diff clarity?

Breaking commit messages at logical boundaries—after sentence-ending punctuation and before enumerated points—isolates changes to specific logical units. This makes version control diffs clearer and helps reviewers understand exactly what changed and why.

When should I apply semantic line breaks to prose instead of fixed line length?

Use semantic line breaks when readability and maintainability matter more than uniform line width: technical documentation, commit messages, code comments, and markdown. This approach preserves meaning across diffs and prevents awkward breaks mid-clause or within hyphenated words.

Can I use semantic line breaks with existing markdown and commit message conventions?

Yes. Semantic line breaks work within standard markdown and commit message formats by respecting line-length guidelines while breaking only at natural stopping points. This maintains compatibility with tools and workflows that expect specific formatting conventions.

What are the limitations of semantic line breaks for very long sentences?

Semantic line breaks work best when sentences are already reasonably structured. Extremely long run-on sentences may still require rewording to break cleanly at independent clauses, and some edge cases around hyphenation or specialized punctuation require manual judgment.