Skip to main content
Watchman reviews activity in your connected repository (pull requests and commits) and analyzes it against your existing test coverage. It’s designed to catch changes that might need test coverage before they merge, without you having to manually cross-reference a diff against your test inventory. You can use Watchman even on a repository you haven’t set as your Test Center source. Connect a repo purely for Watchman analysis by choosing None (Watchman analysis only) when asked which repo should feed Test Center.

​
Analyzing a pull request or commit

Paste a pull request URL, a commit, or ticket text or URL into Watchman’s input. It detects what you pasted and opens a single results tab, labeled Code Review for a pull request or Analysis for a ticket.

​
Pull request summary

For a pull request, Watchman adds a summary layer above the AI analysis, built directly from the pull request’s data:
  • Size: file count, additions, deletions, and which area of the codebase the change is mostly in.
  • Changed Files: the files touched, grouped by purpose rather than listed in raw path order.
  • Notable Changes: flags dependency changes, database migrations, environment variable changes, new or changed API routes, deletions, and changes touching authentication or payment-sensitive paths.
  • A status badge showing whether the pull request is Draft, Open, or Merged (and which branch it merged into).

​
Review target

Watchman can post its analysis back to GitHub, directly on the pull request or commit it reviewed. Set this under Configuration → Watchman → Review Target.
A Linear integration for review destinations is planned but not yet available. The option is shown but disabled in the current release.

​
Turning it on

AI analysis is enabled per workspace under Configuration → Watchman → AI Analysis. There’s nothing further to configure on your end. Once it’s on, Watchman reviews new activity on your connected repositories automatically.