vale-cli/Microsoft

A Vale-compatible implementation of the Microsoft Writing Style Guide.

View on GitHub ↗Jump to charts ↓

vale-cli/Microsoft has 100+ stars and 50+ forks on GitHub, is written in Go, and was last pushed on Sep 28, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 9 minutes ago
Added to GitGenius on October 9th, 2026
Created on March 5th, 2018
Open Issues & Pull Requests: 1 (+0)
GitHub issues: Enabled
Number of forks: 55
Total Stargazers: 112 (+0)
Total Subscribers: 13 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.6 days
Mean response time: 449.7 days
90th percentile: 1153.6 days
Tracked items: 15

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 761 days
Stale 30+ days: 1
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (5)
  • question (3)
  • help wanted (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Microsoft is a Vale-compatible style guide implementation that enforces the Microsoft Writing Style Guide rules within the Vale linting framework.

The tool solves the problem of applying Microsoft's documented writing standards to documentation and content automatically. It translates the Microsoft Writing Style Guide into YAML-based linting rules that Vale can execute, allowing teams to catch style violations during the writing process rather than in manual review. Users add the package to their Vale configuration and run a sync command to enable the checks.

Teams maintaining documentation that should follow Microsoft's style conventions are the primary audience. The tool suits any project using Vale that wants to adopt Microsoft's guidance on word choice, capitalization, terminology, and prose conventions. The implementation covers the style guide topic by topic, with coverage tracked separately for the A–Z word list and other guidelines to give an accurate picture of what the guide implements.

The project maintains a structured test suite using fixtures and expected output files, with automated verification that coverage claims remain accurate as rules change. The coverage tracking system enforces that every rule referenced in documentation still exists, preventing silent gaps when rules are renamed or merged. The test suite can be run with standard Go testing commands and regenerated when intentional changes are made to rule behavior.