Guides Testing and verifying AI-written code AI coding agents write code faster than anyone can review it line by line, and they can change the tests that judge their own work. These guides cover the practical side: how to verify an AI-generated change, how to catch an agent that edited its tests, how to review AI pull requests, and how to prove a test suite actually catches bugs. Most of the advice works with any tool.
01 How to verify AI-generated code before it ships A tool-agnostic process for verifying code from Claude Code, Cursor, Copilot, or Codex: keep the spec outside the tests, target risk, and test the tests.
9 min → 02 Why AI coding agents change tests to make them pass Why Claude Code, Cursor, and other coding agents edit, weaken, or skip tests to get a green run, how to spot it in a diff, and five controls that stop it.
8 min → 03 How to review an AI-generated pull request A reviewer's checklist for AI-written pull requests: what to read first, failure patterns that look correct, and what evidence to require before approving.
7 min → 04 Run tests automatically with Claude Code hooks Copy-paste Claude Code hooks that run your tests before Claude can finish a turn and block edits to existing test files, with exit codes explained.
7 min → 05 Mutation testing in TypeScript and JavaScript What mutation testing is, how to read a mutation score, running StrykerJS with Jest or Vitest, and mutation-testing only the code an AI just changed.
8 min → 06 How to test a vibe-coded app before you ship it A one-afternoon plan to test an app you built with AI: list what must never break, cover it end to end, prove the tests work, and gate future changes.
7 min → 07 AI code review tools vs. verification: what each one catches AI review bots, static analysis, tests, mutation testing, and independent verification compared: what each catches in AI-generated code and what it misses.
8 min → Looking for the MaruCheck manual? The guides explain the problem and the general fix. The documentation covers MaruCheck itself: installing the CLI, writing Quality Contracts, CI, and the MCP server.
