Skills suchen.../

Grammar Check | Skills Pool

Skill-Datei

Grammar Check

Enforces compound-adjective hyphens, articles, and prepositions per Microsoft Writing Style Guide. Use when asked to check grammar.

MicrosoftDocs409 Sterne02.03.2026

Beruf
Kategorien: Codequalität

Skill-Inhalt

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

What to check (in priority order)

1. Compound-adjective hyphens

Hyphenate compound modifiers before nouns:

"High velocity data" → "High-velocity data"
"natural language interface" → "natural-language interface"
"top selling items" → "top-selling items"

Do NOT hyphenate after the noun. Closed forms: "subsecond", "subcategory".

2. Articles

Countable nouns need articles:

"for conversational experience" → "for a conversational experience"
"drops below threshold" → "drops below a threshold"

3. Prepositions

Use natural prepositions:

"experience against data" → "experience with data"

What to ignore

Verwandte Skills

Schnellinstallation

Grammar Check

npx skills add MicrosoftDocs/cloud-adoption-framework

Skill herunterladen Repository öffnen

Autor: MicrosoftDocs
Sterne: 409
Aktualisiert: 02.03.2026
Beruf

Auf dieser Seite

01What to check (in priority order)

Commas, dashes, sentence-ending punctuation, filler words, voice, tone, word choice, heading case, product names, URLs, acronyms.

Rules

Keep fixes minimal — only changed words plus 2-5 surrounding words.
If unsure about a fix, skip it rather than guessing.

02

1. Compound-adjective hyphens

043. Prepositions

05What to ignore

Technische Redakteure

Openclaw Release Maintainer

Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.

Verify

Use when you want to validate changes before committing, or when you need to check all React contribution requirements.

Flow

Use when you need to run Flow type checking, or when seeing Flow type errors in React code.

Automatisierungswerkzeuge

Fix

Use when you have lint errors, formatting issues, or before committing code to ensure it passes CI.

Hygiene

Use when making code changes to ensure they pass VS Code's hygiene checks. Covers the pre-commit hook, unicode restrictions, string quoting rules, copyright headers, indentation, formatting, ESLint, and stylelint. Run the hygiene check before declaring work complete.

microsoft184.0k

Add Policy

Use when adding, modifying, or reviewing VS Code configuration policies. Covers the full policy lifecycle from registration to export to platform-specific artifacts. Run on ANY change that adds a `policy:` field to a configuration property.

microsoft184.0k

Technische Redakteure