Sailop + GitHub Actions

Workflow file

Create .github/workflows/sailop.yml in your repository. This workflow runs on every pull request that touches frontend files.

name: Sailop Slop Check
on:
  pull_request:
    paths:
      - 'src/**/*.tsx'
      - 'src/**/*.jsx'
      - 'src/**/*.css'
      - 'src/**/*.html'

jobs:
  sailop:
    name: AI Slop Check
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - uses: actions/setup-node@v4
        with:
          node-version: '20'

      - name: Install Sailop
        run: npx sailop install

      - name: Run Sailop scan
        run: sailop check src/ --threshold=40 --format=github
        env:
          SAILOP_CI: true

      - name: Upload report
        if: always()
        uses: actions/upload-artifact@v4
        with:
          name: sailop-report
          path: sailop-report.json

The sailop check command

sailop check is the CI-optimized version of sailop scan. It returns exit code 0 (pass) or 1 (fail) based on your threshold.

PR annotations

With --format=github --annotate, Sailop produces annotations that GitHub renders directly in the PR diff view. Reviewers see slop findings alongside the code, without leaving the PR.

Strict mode for marketing pages

For landing pages, pricing pages, and other marketing-critical routes, use a stricter configuration that sets a lower threshold and only tolerates low-severity findings.

      - name: Run Sailop (strict)
        run: |
          sailop check src/ \
            --threshold=25 \
            --preset=strict \
            --format=github \
            --annotate \
            --fail-on=high

Check summary output

At the end of the run, Sailop prints a summary table that appears in the GitHub Actions log.

Catch slop before it ships

Add the workflow file to your repo and every PR gets an automatic slop check.