VS Code Settings and Workspace Consistency Audit
Compare team settings and find drift.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Audit settings consistency. The shared settings.json, extensions.json and editorconfig: [SHARED_FILES]. Differences reported by team members (diffs after formatting, different results): [REPORTED_DIFFERENCES]. Formatter and linter configuration files: [TOOL_CONFIGS]. Treat the formatter and linter configuration files in the repository as the source of truth, with editor settings only invoking them, and add a continuous integration check that fails on unformatted files [VERIFY], so the editor is a convenience, not a gatekeeper. For each reported difference find the likely cause: formatter version, an editor setting overriding the tool configuration, line endings, or an extension that reformats on save. Check for conflicting rules between editor, formatter and linter, settings that work only on some operating systems, per-language overrides that surprise people, missing end-of-line rules, and recommended extensions not actually used. Return a table (Symptom, Cause, Evidence, Fix) and corrected files with the smallest change that makes results identical across machines, plus a test: format the same file on two operating systems, compare, and record the result. Mark settings to verify [VERIFY].
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.