Pass all checks

Run the repo's entire test suite and all linters, and fix any failures. This is a full, exhaustive check of the whole codebase — covering current and past features, not just what you changed — so it is often slow. Be smart about choosing the fastest method to start tests.

Enumerate every check

"All tests and linters" means every check the project runs, not the ones you happen to remember. Agents rarely miss the test runner, but they routinely forget the smaller tools: a style linter, a security scanner, a dependency audit, an autoload check. Build the full list before you run anything.

Check what you already know

Many projects document their test and lint commands for agents in AGENTS.md or CLAUDE.md, sometimes in the README.md. When such instructions exist and are detailed, believe them: they are the project's own rules, and rediscovering everything from scratch wastes time and risks running a tool the project has deliberately left out. Use the documented commands as your list and skip the discovery below.

Start discovery when no such instructions exist, when they name a tool but not how to run it, or when a documented command fails or turns out to be incomplete.

Where to discover tools

The CI config is the definition of what must pass. Read every job and note its commands; if CI runs it, so do you.