
Search Operators
Find notes by date and links, with a preview for each result.
Check CSV values, types and duplicates before you use an export.
MIT · no telemetry · core features free

Phone and tablet use, live GitHub sign-in and paid sponsorship were not tested in this build.
Directory facts fetched from community.obsidian.md/users/theluckystrike.
You keep CSV exports in your vault and need to check their column values before using or sharing them.
CSV Rule Check checks your CSV against a rule file beside it. You get logical row numbers, column names and failed rules. Write a Markdown report to keep the result.
Play demoChoose a CSV already in your vault. For people.csv, put the rules in people.csv.schema.json beside it. Missing files, invalid JSON and unknown rule keys stop the check.
Check required values, string, number and boolean types, allowed values and uniqueness. Comparisons preserve case and spaces. Number checks leave text such as 001 unchanged.
Row 1 is the header, and quoted line breaks stay inside one logical record. Results show up to 500 errors and the total count. Duplicate headers stop the check.
Write a snapshot of the last successful check beside the source CSV. Numbered report names avoid existing files. The report includes the source path, record count and displayed errors.
Fix previews, corrected CSV copies, saved rule sets and batch checks need Pro.
Pro costs $5 a month or $15 one time through GitHub Sponsors. One sponsorship turns on Pro in every plugin that has it.
Add trim or string defaults to your rules, then preview before and after values. Trim runs before defaults. Write a separate CSV copy; a changed source stops that write.
Save a copy of a checked schema under a new name. Choose that rule set and 1 to 20 CSV files for a batch. A file that cannot be checked stops the new batch.
needs
steps
Put the CSV and its adjacent JSON rule file in your vault.
Run Choose CSV and check adjacent rules from the command palette.
Select the CSV and inspect the results table.
Correct the source in your CSV editor, then check again.
Select Write report to save the last successful check.
If the app can't find a new plugin yet, try again later. Obsidian says a plugin that passes the review shows in the app within 24 hours.
Need a change for your team? I build custom Obsidian plugins and features.
No, you write the rules in JSON. A clean result means those rules passed, rather than proving your business records are correct.
The required rule checks for an empty field. Spaces count as a value, and case and spaces affect allowed-value and duplicate checks.
The CSV and rule file each have a 5 MiB limit. The checker reads complete files into memory and stores up to 500 errors per file.
Trim and defaults change only whitespace and empty values. Invalid numbers, wrong allowed values and duplicate identifiers can remain in the copied CSV.
After you choose Sign in with GitHub, github.com receives the public client ID, profile scope and device-flow polling requests. After sign-in, api.github.com receives an authenticated query for your sponsorship tier and total payment; neither host receives vault data. Successful checks last seven days; network failures can retry after six hours, and Refresh requests an earlier check.
Tell me what is broken in CSV Rule Check, or what it should do next.
CSV Rule Check 1.1.0, MIT license
MIT · no telemetry · core features free