Problems (governance & lint checks)

Run policy, release-lane, and lint checks on the current file — draft, standard, or strict.

Preview — early access.

Overview

The Problems strip at the bottom of the editor runs the same governance and lint checks a person would before shipping a change — policy evaluation, release-lane classification, and ESLint diagnostics — scoped to the file you have open.

How it works

Click Run checks (or press ⌘⇧G / Ctrl+Shift+G) to run all three: a policy check, a release-lane read, and lint. Results show a pass/fail badge per layer, with lint diagnostics you can click to jump straight to the offending line. A governance mode controls when checks run automatically: draft only runs on demand, standard re-runs after every save, and strict does the same but shows a blocking banner (editing itself is never blocked) when policy or lint comes back failing. Disagree with a policy result? Flag policy lets you say why, right from the strip.

Steps

•
Open a file
The Problems strip sits at the bottom of the editor, below Comments.
•
Pick a governance mode
Draft (manual only), Standard (checks on save), or Strict (checks on save + a blocking banner on failure).
•
Run checks
Click "Run checks" or press ⌘⇧G / Ctrl+Shift+G.
•
Read the results
Policy outcome, release lane, and lint diagnostics each show their own status.
•
Jump to a lint issue
Click a diagnostic to move the cursor straight to that line and column.
•
Flag a policy you disagree with
Click "Flag policy" and say why — it's logged for review, not silently overridden.

Capabilities

Three checks in one run — policy evaluation, release-lane classification, and ESLint.
Three governance modes — draft (on demand), standard (on save), strict (on save + blocking banner).
Keyboard shortcut — ⌘⇧G / Ctrl+Shift+G runs checks without leaving the keyboard.
Click-to-jump lint diagnostics.
Policy flagging — disagree with an outcome and it routes to review instead of just being ignored.

Limits & honest scope