Meta Commit Guard
Catch missing .meta files, duplicate GUIDs, and risky asset references before commit. Review clear Git-aware evidence locally or in CI without changing project files.
by Kevin Bjorvand
Price History +
🔍 Catch Small Problems Before They Spread
A missing .meta file or duplicate GUID can turn a simple commit into broken references, missing assets, and hours of cleanup.
Meta Commit Guard checks these problems before they reach your team. It gives you clear evidence, so you can fix the right file before you commit or merge your work.
🎯 Find the Exact Cause
The tool finds assets without matching .meta files and .meta files without matching assets. It also detects malformed GUIDs and duplicate 32-character GUIDs.
For supported references, results can show the exact file, line, column, asset type, and nearby context. This helps you understand what may be affected without searching the whole project by hand.
📂 Know What Was Checked
Staged changes, unstaged changes, project files, and uninspected files stay in separate groups.
You can clearly see what was checked and what could not be checked. Binary, unreadable, unsupported, oversized, or changing files are marked as uninspected instead of being silently ignored.
🚦Use It Before Commits or in CI
Run a review inside the Editor before you commit. Use project badges to keep important findings visible while you work.
For automated checks, Meta Commit Guard creates repeatable text and JSON reports. Its batch mode can stop a CI job when selected problems are found.
A manual Git hook command is also included. The tool never installs hooks by itself.
🛡️ Read-Only and Safe
Meta Commit Guard does not repair files or rewrite GUIDs. It does not stage, restore, check out, commit, or create branches.
It also does not contact the internet. Your project and Git state stay under your control.
