Setting Up Automated AI Code Forensics with the VibeFix GitHub Bot

You can't manually review every single line of AI-generated code your team outputs. To scale, you need automation. That's where the VibeFix GitHub Bot comes in.

This guide will walk you through turning VibeFix from a passive monitoring tool into an active gatekeeper for your main branch.

## Step 1: The Installation

Head to the VibeFix dashboard and click "Install GitHub App." You can apply it to specific repositories or your entire organization. Once installed, VibeFix automatically begins analyzing every new Pull Request.

## Step 2: Defining the Baseline

By default, VibeFix runs a comprehensive scan of your existing codebase to establish a historical baseline. This is crucial. If your legacy code has a Vibe Score of 60, VibeFix won't aggressively fail new PRs that score a 65. The goal is *progressive improvement*, not immediate perfection.

## Step 3: Setting Up PR Guardians

This is where the magic happens. Navigate to your repository settings in the VibeFix dashboard and configure your Guardian rules:

- **The Hard Gate:** Reject any PR with a Vibe Score lower than X (e.g., 50).

- **The Relative Gate:** Reject any PR that lowers the repository's overall average score by more than 2 points.

- **The Slop Threshold:** Auto-request changes if the PR contains more than 15% identified "AI Boilerplate."

## Step 4: The Developer Experience

When a PR is opened, VibeFix runs its analysis in seconds.

If it passes, the developer gets a green check and a summary of their Vibe Score.

If it fails, VibeFix doesn't just block the merge; it leaves actionable inline comments explaining exactly *why* the code was flagged as AI slop and *how* to rewrite it to meet the repository's human standards.