What it does
AI chat answers often come with small problems that stop code from running: it is cut off, has "rest of the code" placeholders, curly quotes, chat sentences mixed in, or stray invisible characters. Paste the answer and the tool lists each problem with its line, column, severity and an explanation. Each fenced code block is found and checked on its own, and the language is guessed (or you choose it).
What it checks
- Code fences and their language tags, and a fence that is never closed.
- Truncation: unclosed or mismatched (), [] and {} (strings and comments are ignored), strings, template literals and block comments that never end, invalid JSON, and a last line that ends with an operator, comma or colon.
- Placeholders: a line that is only "...", comments such as "rest of the code" or "existing code here", TODO and FIXME comments, Python bodies that are only
pass, "not implemented" errors and values such asyour_api_key_here,<YOUR_KEY>,xxxxorchangeme. A "..." inside a string or a spread operator such as...argsis not flagged. - Typographic characters in code: curly quotes, en and em dashes and non-breaking spaces. Curly quotes where a code quote belongs are errors; inside a string or comment they are warnings.
- Mixed tabs and spaces in indentation.
- Chat text: lines such as "Here is the updated code", "Certainly", "I hope this helps" or "As an AI" outside the code.
- Invisible characters: only counted here. Use the Hidden Unicode Detector to see and remove them.
Full verification chain
The button Run full chain checks the whole answer in seven steps and joins the results into one report. Each step uses the engine of another DevToolEra tool, so the rules are the same as in that tool: Hidden Unicode Detector (including text hidden in tag characters), Secret Scanner, AI Code Risk Linter (each code block by its own language), Shell Command Risk Explainer (shell blocks and install or download commands), and the offline part of the Package Existence Checker. The seventh step looks for license markers such as SPDX lines, GPL-family text and "all rights reserved". A step whose engine cannot be loaded is marked "Not available" and the others still run.
The report has a scoreboard, the findings of each step with their line numbers in the text you pasted, and a list of what the chain cannot catch. You can copy it as Markdown. Copy cleaned code joins the code blocks and applies only the clean-ups you tick. Copy redacted code masks possible secrets. Check on registries opens the Package Existence Checker with the package names found; this page itself never contacts a registry, and the Package Checker asks before it does.
The wording of the result is deliberately cautious. "No issues found by these checks" means these rules found nothing; it does not mean the code is correct, safe or free of license obligations.
Clean copy
The clean copy applies only the fixes you tick: remove code fences, straighten curly quotes that are used as code quotes, and remove chat lines. Curly quotes inside strings and comments are left alone unless you also tick that option. Dashes, spaces and everything else are never changed. The changed lines are shown before you copy, and nothing is changed automatically.
What it cannot catch
- Wrong logic, wrong results or bugs: the tool does not run or understand the code.
- Wrong or invented APIs, functions, options or file paths, and packages that do not exist. Check every import against the real documentation.
- Missing code that leaves the brackets balanced, a placeholder written in an unusual way, and chat text that does not match its list of phrases.
- Bracket checks work for JavaScript or TypeScript, Python, JSON and SQL, not for shell or "Other". The scanner is a simplified one: unusual syntax (JSX text with apostrophes, regular expressions after a closing parenthesis) can cause a false alarm.
- A clean result is not proof that the code works.
Limits
Text up to 2,000,000 characters is checked. The table lists the first 500 findings. Everything is processed in the page, so a very large paste can take a moment. The full chain accepts up to 1,000,000 characters and keeps the first 300 findings of each step. If you use Send to or Check on registries, the text or the package names are held in your browser session storage for up to one minute so the next page can read them, and are then removed.
Privacy
This tool runs entirely in your browser. What you enter is processed on your device and is not sent to a server. The page does not write your input to local storage, cookies or the URL.