Claude · Mistakes

Verification mistakes

Check summaries against the source and code by running it, ignore confident wording, and keep hard decisions for yourself.

Checking Claude's work

Match the check to the claim

Different outputs fail in different ways, so one habit won't cover them. For a summary, read the quote against the claim. For a fact or number, open a source. For code, run it and read the output. For a decision, ask what Claude can't see. The cards in this lesson take these one at a time, each with a prompt that makes checking quicker.

Where checking can be automated

In Claude Code, part of this can be enforced by the tool. A Stop hook can keep Claude working until a check passes, and /code-review runs in a fresh subagent that didn't see your conversation. In the chat app, you do the checking, with help from citations when Claude uses web search. Neither replaces your judgment on work that matters.

Frequently asked
How do I fact-check Claude's answers?

Ask for a source for each specific claim, and open the ones you'll rely on. Turn on web search for anything that changes. Anthropic notes that some links may not work, so confirm the page says what the answer says.

Are Claude's citations reliable?

They give you a place to check. Anthropic says its API citations are guaranteed to point to valid locations in the documents you provide, but you still need to read whether the passage supports the claim.

Should I test code that Claude writes?

Yes. Anthropic's Claude Code guide says Claude stops when work looks done, so give it a test, build or linter to run, and ask to see the command and its output.

Can Claude check its own work?

Partly. It can run tests and compare a draft to criteria, and Anthropic says this helps. Its Fable 5 guide says fresh-context verifiers tend to outperform self-critique, and high-stakes work still needs a qualified person.