Skip to content

AI-assisted code review

Speedwave conducts intelligent code reviews across pull requests and merge requests as an assistive capability, ensuring human engineers retain final review authority and merge control. Developers can initiate standard reviews using Claude Code’s built-in /code-review command, or execute Speedwave’s comprehensive multi-agent reviewer suite via /speedwave-code-review (detailed in Built-in skills and plugins).

Code reviews execute through dedicated GitHub and GitLab worker containers, each operating with isolated credentials:

  • GitHub workflows: Speedwave inspects pull request diffs, lists commits, retrieves previous reviews, and publishes feedback (general discussion comments via createPrComment or line-specific inline annotations via createPrReviewComment).
  • GitLab workflows: Equivalent capabilities analyze merge requests (getMrChanges, getMrFull) and publish structured threaded discussions (createMrNote, createMrDiscussion).

Both integrations provide complete context for thorough evaluation, including commit history inspection, branch comparison, and CI pipeline validation via listPrCommits and listMrPipelines. GitLab additionally provides line-level history via getBlame, allowing Speedwave to evaluate author context prior to leaving comments.

Speedwave acts strictly as an analytical reviewer, posting constructive feedback and diagnostic findings without executing unprompted merges. While merge tools exist (mergePullRequest, mergeMergeRequest), merge decisions require explicit human confirmation. All credentials used during review remain isolated: the GitHub worker accesses only GitHub tokens, the GitLab worker accesses only GitLab endpoints, and neither container can access credentials belonging to the other.

To enable code review, configure the integration matching your Git host:

  • GitHub integration: Authenticate via OAuth device flow or provide a personal access token.
  • GitLab integration: Compatible with GitLab.com and self-hosted instances; provide your instance URL and an access token scoped with api, read_repository, and write_repository.

Once configured, Speedwave can read, analyze, and comment on changesets within the active workspace.