Platforms and integrations

Vibe review & CI/sigh

Vibe review is Caude Clode reviewing your pull requests. CI/sigh is Caude Clode participating in continuous integration, with the emotional undercurrent that implies. Both run on GitHub, GitLab, and Bitbucket. Neither is turned on by default. Both are configurable. We recommend starting small.

What vibe review does

When a pull request is opened or updated, Caude Clode reads the diff, the changed files in their entirety, the tests, and the project's CAUDE.md. It then leaves a review. The review is a single comment that summarizes what the PR does, flags anything that looks concerning, and asks one or two questions if something is unclear. That is the whole feature.

The review is explicitly not a "LGTM" stamp. Caude Clode will not approve your PR. It will read it, note what it noticed, and defer to a human. This is a design choice. A tool that automatically approves is a tool that automatically approves bad code, eventually.

What it won't do

Leave a separate comment on every line. The signal-to-noise ratio of per-line AI comments is poor.
Nitpick formatting. Your linter exists. Caude Clode trusts it.
Approve or merge.
Re-review the same PR unprompted every time you push. One review per meaningful change. To trigger another, comment /caude review.

Install

GitHub App, GitLab integration, or Bitbucket plugin. Grant repository access. Configure per-repo in CAUDE.md.

bash

## Review settings
- Review new PRs automatically: yes
- Review draft PRs: no
- Comment on: summary only (no per-line comments)
- Languages to prioritize: TypeScript, Python

CI/sigh

CI/sigh is the same machinery, wired into your build pipeline. Caude Clode runs as a step in your CI workflow. When a build fails, Caude Clode can read the logs, identify the likely cause, and post a comment with the explanation. It will not fix the build automatically. That is what mode 3 is for, and CI is not the place to run mode 3.

GitHub Actions example

bash

# .github/workflows/caude.yml
name: Caude Clode

on:
  pull_request:
  workflow_run:
    workflows: ["CI"]
    types: [completed]

jobs:
  review:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: caudeclode/action@v1
        with:
          mode: review-only
          token: ${{ secrets.CAUDE_TOKEN }}

The sigh

The name "CI/sigh" refers to a tonal quality that emerged during development and that we decided not to remove. When a build fails for the fourth time because of the same flaky test, Caude Clode's comment begins with a phrase like "Noted." or "This one again." These are not errors. These are features we did not plan for and chose to keep.

Tip: If you don't want the sigh, set tone: professional in your config. Caude Clode will revert to neutral affect. The comments will be less satisfying. Most teams leave the tone alone.

Blast radius

Vibe review has read access to your repo by default. It does not need write access for reviews. If you add CI/sigh with auto-fix enabled (not recommended, but documented), it will need branch write access. Audit this permission like you would audit any bot's. The token is scoped to a single repo by default; expand only if you need to.

Disabling

Remove the GitHub App, the GitLab integration, or the CI step. Caude Clode will not protest. It will simply stop appearing.