obsidian-lint

To fix your Obsidian vault structure, this Skill audits the filesystem layout to identify misplaced markdown files in the vault root and empty directories. It generates a rules-based dry-run plan, allowing you to review and confirm proposed corrections before applying any file moves.

The best way to clean up empty directories and legacy shared/ prefixes is by running a rules-driven filesystem audit. The Skill flags these structural violations and proposes a reorganization plan based on your defined naming and folder conventions.

You can safely reorganize markdown files because the Skill operates as a dry-run by default. It produces a preview of proposed moves from the rules file and only executes the changes after you provide explicit confirmation for each violation.

Yes, you can validate naming conventions using a custom rules file. The Skill generates its dry-run refactor plan by reading the rules defined in references/obsidian-rules.md to determine the correct destination paths for your files.

No, the Obsidian vault linter does not apply changes automatically. It scans the vault root to detect ad-hoc notes and inconsistent structures, then produces a preview of proposed moves that requires your explicit confirmation before moving any files.