em-dash style

Identify and replace em-dash characters in Markdown documentation.

3|2|Updated May 12, 2026
One-click install
npx skills add https://github.com/kriscendobot/garden --skill em-dash-style
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: em-dash style
Source: https://github.com/kriscendobot/garden/tree/main/skills/em-dash-style
Command: npx skills add https://github.com/kriscendobot/garden --skill em-dash-style

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the tendency for em-dashes to clutter technical documentation and obscure the rhythm of prose, ensuring a consistent and professional writing style across all project documents.

Core Features & Use Cases

  • Prose Standardization: Automatically identifies and flags em-dashes in Markdown files while preserving code blocks and en-dash numeric ranges.
  • Contextual Rewriting: Provides clear guidance on replacing em-dashes with periods, parentheses, or colons based on the intended grammatical structure.
  • Use Case: Use this skill to audit a new documentation pull request to ensure it adheres to the garden's strict style guide before merging.

Quick Start

Ask the garden to scan the current directory for em-dashes and suggest replacements for any found instances.

Frequently Asked Questions about em-dash style

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

FAQPage Schema
How do I remove em-dashes from Markdown documentation to improve prose readability?

You can remove em-dashes from Markdown documentation by scanning project prose files and replacing the characters with periods, parentheses, or colons. This enforces a consistent, professional writing style across technical documents.

Why do em-dashes clutter technical documentation and what style replacements should I use?

Em-dashes clutter technical documentation by obscuring the rhythm of your prose. You should replace them contextually with periods for distinct sentences, parentheses for supplementary information, or colons for direct elaboration.

Does this prose style checker preserve code blocks and en-dash numeric ranges in Markdown?

Yes, the prose standardization process preserves code blocks and en-dash numeric ranges. It specifically targets em-dash characters in standard prose while excluding vendored references and code-formatted content.

What's the best way to audit a documentation pull request for strict style guide adherence?

The best way to audit a documentation pull request is to scan the directory for em-dashes and suggest grammatical replacements. This verifies that new contributions adhere to strict style guidelines before merging.

Do I need standard grep utilities to perform project-wide Markdown file filtering?

Yes, you need standard grep utilities to perform pattern matching and file filtering. The exclusion rules rely on these utilities to accurately bypass vendored references and code-formatted content.