Run Tests

Find out if this project has tests, run them the way the project intends, and report what actually happened. The single biggest failure mode is running the wrong command confidently: a bare pytest in a uv project, bun test where only bun run test excludes integration suites, or Django tests without the flags its Makefile encodes. The project always knows better than memory — this skill's job is mostly to find where it wrote that down.

1. Read the project's own instructions first

Before touching a test runner, read what the repo says about testing:

• AGENTS.md / CLAUDE.md (root and relevant subdirectories)
• .cursor/rules/*.mdc — rules marked alwaysApply bind here too (venv activation requirements commonly hide there, not in AGENTS.md)
• CONTRIBUTING.md and docs/ testing sections
• CI workflows (.github/workflows/*.yml) as a last-resort source of truth for how tests really run