One file. Every note. Every line of code.

Lynter applies one reviewed lynter.yaml in Obsidian, the CLI, CI, and agent workflows, scoped to each folder, tag, or language.

Edit the config or the note. This is the real rule engine, running in your browser.

Result
---tags: [weekly, review, planning]status: drafttitle: Weekly review---# Weekly review## What Went Well This WeekIt is **really** important that we do not lose momentum.We shipped the importer and it is already in use.
Profiles applied: Nothing to change. The note already follows this config.

The config is a file

Rules live in lynter.yaml at the root of your vault or repository, not in plugin settings. Every change shows up in a diff and goes through review like code.

Scopes inherit

Match folders, tags, properties, or languages. Each scope starts from the base and states only what differs, so a client folder can stay formal while the rest stays casual.

Same result everywhere

Obsidian, the command line, CI, and agent hooks run one rule core. A note that passes in Obsidian passes in the pre-commit hook and in CI, with no API tokens.

Pick a folder to see which rules apply

Deeper scopes override broader ones. This is the same resolution the explain command prints for a path.

Profile chain
Contractions
on

Run it in hooks and CI

check exits 1 when a file breaks a rule. fix rewrites in place. --changed limits either to the files git sees as changed.

# check notes git sees as changed, before a commit
lynter check --changed

# fix a folder in place
lynter fix notes/

# show which profiles govern a path
lynter explain work/projects/client/brief.md

How it compares

LynterObsidian Lintermarkdownlint
Config in a git-tracked fileYes, lynter.yamlNo, plugin data.jsonYes
Rules scoped by folder, tag, or propertyYes, with inheritanceNoNo
Frontmatter schemas per note typeYesNoNo
Same engine in Obsidian and CIYesNoSeparate plugin and CLI
Code linting from the same fileIn progressNoNo

Common questions

Does Lynter call a model?

No. Every rule is deterministic code. The same input gives the same output, with no tokens and no network.

Is it available in the Obsidian directory?

Not yet. You can install the plugin from a clone of the repository today.

Which languages does it lint?

The first release targets Rust, Python, TypeScript, JavaScript, SQL, Go, Java, C#, JSON, YAML, and text. Code linting is in progress.

Already use Obsidian Linter?

Paste its data.json and get a lynter.yaml. Nothing leaves your browser.