What is better enforced by an automated check than by asking the agent?
Answer out loud or in your head first, then compare.
Answer
Things that can be checked unambiguously: type checking, formatting, important tests and detecting some secrets. The instruction “always check the tests” is an expectation. The actual output of a command is evidence, and CI, i.e. automatically checking each code change, can block merging a broken change. GitHub Actions lets you run such tests, as well as build and deploy the app, after certain repository events.
A hook is a mechanism that runs on a specific tool event. It can help with control, but you need to know its real blocking rules. The scripts and CI configuration themselves need protecting too. An agent could weaken a test to “fix” it. So a review also covers changes to assertions and configuration. Green checks don't cover requirements nobody wrote down.
Why it matters: Connects working with an agent to trustworthy verification.
Possible follow-ups: Is the agent's message “tests passed” enough without the run's output?
How did it go? Be honest — “Not yet” puts the question on your review list.
Start with
- I-P01 · What is an agent harness? — Harness, MCP and coding agents
- I-P02 · What is MCP? — Harness, MCP and coding agents
- I-P04 · How does a coding agent differ from a chat that suggests code? — Harness, MCP and coding agents
Further reading
- GitHub: Understanding GitHub Actions(opens in a new tab)Accessed 22.10.2026. Automated testing, building and deployment triggered by repository events.
- Anthropic: Effective harnesses for long-running agents(opens in a new tab)26.11.2025. Working in stages, progress artifacts and resuming between sessions.