slop

Slop Command

Check the diff against main and remove all AI-generated slop introduced in this branch.

What is "Slop"?

AI-generated code often has tells that make it look unnatural:

1. Over-Commenting

// BAD: AI slop
// Get the user from the database
const user = await db.getUser(id); // Fetch user by ID

// GOOD: Self-documenting, no comment needed
const user = await db.getUser(id);

2. Defensive Overkill

// BAD: Unnecessary defensive checks
function processUser(user: User) {
  if (!user) {
    throw new Error('User is required');
  }
  if (!user.id) {
    throw new Error('User must have an id');
  }
  // ... when caller already validates
}

// GOOD: Trust internal callers
function processUser(user: User) {
  // Just do the work - caller handles validation
}

3. Type Escapes

// BAD: Casting to escape type issues
const data = response as any;
const items = (result as unknown as Item[]);

// GOOD: Fix the actual type
const data: ResponseType = response;

4. Inconsistent Style

• Different naming conventions than the file uses
• Different error handling patterns
• Different import styles
• Added JSDoc when file doesn't use it (or vice versa)

5. Unnecessary Try/Catch

// BAD: Wrapping things that don't throw
try {
  const x = a + b;
  return x;
} catch (error) {
  console.error('Failed to add numbers', error);
  throw error;
}

// GOOD: Just do it
return a + b;

6. Verbose Logging

// BAD: Logging everything
console.log('Starting process...');
console.log('User ID:', userId);
console.log('Processing...');
console.log('Done!');

// GOOD: Log meaningful events only (or nothing for simple ops)

Workflow

1. Get the Diff

git diff main...HEAD

Identify all files changed in this branch.

2. For Each Changed File

1. Read the FULL file (not just the diff) to understand existing patterns
2. Compare new code against existing style:
   • Comment density
   • Error handling approach
   • Naming conventions
   • Type annotation style
   • Import organization