Pre-flight lint for mr-content

What it does

Checks your content against the team's building & house-style rules and lists every issue in one report, grouped by severity, with a copy-paste fix-prompt. It never changes files.

When to use it

Right before you push your branch — a final gate to catch slips (duplicate icons, "and" vs "&", missing scoring, broken references) that are easy to miss page-by-page.

How to use it

1. Connect your mr-content folder once (status pill, top-right — Chrome or Edge).
2. Pick a scope: Changed paths (paste your branch's changed files — the daily gate), A folder / client, or Whole repo (a full audit — slower).
3. Click Run lint. Read the report: blockers must fix, warnings worth a look, info optional.
4. Hit Copy fix-prompt on any group and paste it to Bud, or Download report.

Changed paths — the branch gate

In Terminal, inside your repo, run git diff --name-only master...HEAD (or git status --porcelain), copy the output, and paste it into the Changed paths box. mrguard lints exactly those files, resolving references against the whole repo.

The rules

Duplicate icons / banners in a menu, broken references, slug > 50 chars, missing values banner / #### heading, wrong heading level, "and" that should be "&", stray tags: on a page, repeated words, placeholder text (TODO/TBD…), broken clone:, has-scoring with no committed scoring, surv-common-js not first, orphan locale files, notification window-schedules that may not fire, and clients missing from whitelists.

Good to know

• mrguard only reads your files — nothing is written, nothing leaves your computer.
• House-style checks match mrview exactly (same engine) — no surprises between the two tools.
• Reference resolution (broken refs, clones) always uses the whole repo, even when you scope to a folder or your changes.