XML Validation After File – Edits Lint on Code

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

When editing TextMate Bundle files (.tmCommand), which are XML plists, Claude repeatedly inserted Python code containing < characters without escaping them as &lt;. This resulted in broken XML files that TextMate could not load — and the error was only discovered after committing.

Specifically: Claude inserted if prim_cnt[n] < 2:, which is invalid in an XML context. The correct form would be &lt;.

Proposed Solution

A Linter who checked the code before publishing like Codex has.
Suggestion: Claude should automatically run a validation tool (e.g. xmllint) after editing XML-based files, before committing — similar to how Codex uses linters. This would prevent broken commits and make the workflow significantly more reliable.

Alternative Solutions

No alternative: This should be standard.

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

To be honest: I have seen also a comparison video of Codex and Claude. The code from Codex was better, because Codex always lint the code before publishing.
And this is also what I experienced in the past. A lot of the XML are corrupted and I have to fix it first.