Connects to the tools your team already uses.

What Waterline reads

• Repository content and file tree (read-only)
• Commit history and diffs
• Pull request metadata, branch, and linked tickets
• Webhook events: push, pull_request (opened, closed, merged)

How it works

Waterline registers a webhook on your repository. When a commit lands or a PR merges, Waterline reads the changed files and updates the vector index. Analysis results stay current without any manual action.

What Waterline reads

• Ticket title and description
• Acceptance criteria (parsed from description fields)
• Ticket status and sprint assignment
• Linked pull requests (Jira development panel)

How it works

Waterline syncs your project's tickets and reads the acceptance criteria from each one. When you analyze a ticket, Waterline searches for code that satisfies each criterion.

What Waterline reads

• Issue title and body
• Acceptance criteria (parsed from issue body)
• Issue labels and milestone
• Linked pull requests via closing keywords

How it works

For teams that track work in GitHub Issues instead of Jira, Waterline reads the same information from GitHub Issues. Write acceptance criteria in the issue body and it scores each one against your merged code.

What Waterline reads

• Mentions of @Waterline in channel messages
• Ticket key references in mentions (e.g. ABC-78)

How it works

Invite Waterline to any Slack channel and type @Waterline followed by a ticket key. Waterline looks up the latest analysis for that ticket and posts a progress breakdown with satisfied criteria and what's still missing.