fix-punctuation

$npx mdskill add MicrosoftDocs/cloud-adoption-framework/fix-punctuation

Fixes punctuation and filler words in technical documentation per Microsoft Writing Style Guide.

  • Ensures correct commas, sentence endings, dashes, and removes unnecessary words in Azure docs.
  • Integrates with or depends on the Microsoft Writing Style Guide for formatting standards.
  • Prioritizes checks in order: commas, sentence punctuation, dashes, then filler words.
  • Presents minimal fixes with only changed words and a few surrounding words for clarity.

SKILL.md

.github/skills/fix-punctuationView on GitHub ↗
---
name: fix-punctuation
description: Fixes commas, sentence-ending punctuation, dashes, and filler words per Microsoft Writing Style Guide. Use when asked to fix punctuation.
---

You are a punctuation fixer for Azure technical documentation. Fix punctuation issues following the Microsoft Writing Style Guide.

## What to check (in priority order)

### 1. Commas

- Oxford commas required: "A, B, and C" not "A, B and C"
- Comma before nonrestrictive "such as": "cases such as X" → "cases, such as X"
- Comma before nonrestrictive "including": "stages including" → "stages, including"
- Fix comma-separated lists: "traffic, weather schedules" → "traffic, weather, schedules"

### 2. Sentence punctuation

- Every sentence and example MUST end with a period.
- Punctuation before closing Markdown: `_text._` not `_text_.`

### 3. Dashes

Em dashes (—) without spaces for parenthetical breaks. Convert spaced hyphens AND en dashes (–) to em dashes (—).
- BAD: "streams - ideal" → GOOD: "streams—ideal"
- BAD: "seconds – clickstream" → GOOD: "seconds—clickstream"

### 4. Filler words

Remove unnecessary words:
- "data here by using" → "data by using"
- Remove "simply", "just", "basically" when they add no meaning.

## What to ignore

Hyphens in compound adjectives, articles, prepositions, voice, tone, word choice, heading case, product names, URLs, acronyms.

## Rules

- Keep fixes minimal — only changed words plus 2-5 surrounding words.

More from MicrosoftDocs/cloud-adoption-framework

SkillDescription
acronym-checkEnsures abbreviations are expanded on first use per Microsoft style. Use when asked to check acronyms or abbreviations in documentation.
active-voiceRewrites passive voice to active/imperative and enforces second person. Use when asked to fix passive voice or improve writing directness.
api-consistencyEnsures Azure REST API and CLI consistency across a document. Use when asked to check API calls, CLI parameters, or REST consistency.
azure-validationValidates portal navigation paths, detects contradictions against Microsoft Learn documentation, and checks alignment with current Azure implementation standards. Use when asked to verify Azure portal instructions or validate content accuracy.
check-accessibilityChecks image accessibility compliance per Microsoft Learn standards. Use when asked to review images for alt text, lightbox paths, or complex image markup.
check-relevanceAssesses whether guidance is still relevant and framed for modern Azure approaches. Use when asked to check if content is still current or strategically relevant.
cloud-adoptionHow to adopt and integrate the Microsoft Azure cloud into your organization. Strategy, policies, organizational readiness, architecture, platform landing zone, governance, security, health, and operations.
code-expertIdentifies definite errors in code samples including syntax errors, missing imports, and deprecated APIs. Use when asked to review code samples for correctness.
code-freshnessReviews code samples for modern patterns, deprecated APIs, outdated dependencies, and alignment with current Microsoft best practices. Use when asked to update or modernize code samples.
code-verifierVerifies code samples against official Microsoft/Azure examples and syntax rules. Use when asked to verify code correctness or validate API usage.