AI Janitor PR Workflow

AI Janitor generates pull requests to remove stale feature flags from your codebase. Each PR is structured, reviewable, and follows your team's existing code review process — because AI writes the diff, but humans make the final call.

PR Lifecycle

What the PR Looks Like

Every AI Janitor PR follows a consistent, review-friendly template. Here's an example of what your team will see:

1. 1

   1. AI analyzes the flag

   For each stale candidate, AI Janitor examines the flag's evaluation history, the source code references, and the surrounding code context to determine:

   • Which code path is always taken (the "active" branch)
   • Whether the flag check can be removed without side effects
   • If any imports, variables, or functions become unused after removal
   • Whether the removal affects test coverage
2. 2

   2. Branch is created

   AI Janitor creates a new branch in your repository following the naming convention:

   BashCopy

   1

   2

   3

   4

   5

   # Branch naming pattern (configurable)
   ai-janitor/remove-{flag-key}-{timestamp}
   
   
   # Example
   ai-janitor/remove-new-checkout-20260115
   

   The branch is created from the default branch (main/master) at the time of scan. If the default branch has advanced significantly since the scan, you may need to update the branch before merging.

3. 3

   3. Flag check is removed from each file

   AI Janitor surgically removes the flag evaluation while preserving the active code path. Here's an example of what the diff looks like:

   Example diffDiffCopy

   1

   2

   3

   4

   5

   6

   7

   8

   9

   10

   11

   12

   13

   14

   15

   16

   // Before (with flag check)
   async function checkout(user: User) {
   -  const useNewCheckout = await client.boolVariation(
   -    'new-checkout',
   -    { key: user.id },
   -    false,
   -  );
   -
   -  if (useNewCheckout) {
   -    return renderNewCheckout(user);
   -  }
   -  return renderLegacyCheckout(user);
   +  return renderNewCheckout(user);
   }
   
   
   // After (flag removed, active path preserved)
   

4. 4

   4. PR is opened

   The PR includes all the information your team needs to review with confidence:

   • Automated labels (configurable via pr_labels)
   • Link back to the AI Janitor scan report
   • Confidence score and reasoning
   • Checklist for human reviewers
   • Diff for each changed file

Review Process

AI Janitor PRs integrate with your existing code review workflow:

Auto-Merge Configuration

To enable auto-merge, configure these options in your .ai-janitor.json:

{
  "auto_create_prs": true,
  "auto_merge_prs": true,
  "min_confidence_score": 90,
  "auto_merge_conditions": {
    "require_ci_pass": true,
    "require_no_conflicts": true,
    "require_approved_review": false,
    "max_files_changed": 10,
    "max_lines_changed": 200
  }
}

Next Steps