One-click install
npx skills add https://github.com/DeevsDeevs/agent-system --skill anti-ai-slop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: anti-ai-slop
Source: https://github.com/DeevsDeevs/agent-system/tree/main/anti-ai-slop
Command: npx skills add https://github.com/DeevsDeevs/agent-system --skill anti-ai-slop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill reviews the diff against main and removes changes that are likely “AI slop”: unnecessary, non-idiomatic, or inconsistent additions that do not materially contribute to the intended feature/fix.

Core Features & Use Cases

  • Determines the appropriate diff source in the correct order (cached diff, working diff, or main vs HEAD) and avoids unrelated refactors.
  • Enforces the principle of minimal, idiomatic changes and preserves meaningful changes while pruning noise.
  • Useful in feature branches, code reviews, and collaborative projects to maintain clean, auditable histories.

Quick Start

Run the diff cleanup on your current branch to remove AI-generated slop while preserving essential changes.

Frequently Asked Questions about anti-ai-slop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I remove AI slop from a git diff before code review?

To remove AI slop from a git diff, the skill identifies unnecessary or non-idiomatic additions and strips them out, preserving only meaningful changes. It targets diffs between branches or main to enforce minimal, idiomatic edits per repository conventions.

What is AI slop in a code diff?

AI slop in a code diff consists of unnecessary, non-idiomatic, or inconsistent additions that do not materially contribute to the intended feature or fix. It often results from broad refactors that introduce noise into the working diff.

How do I clean up unnecessary changes in my feature branch diff?

You can clean up a feature branch diff by running the skill to automatically determine the correct diff source, such as cached or working diff. It prunes noise and avoids unrelated refactors while keeping essential changes intact.

Does this diff cleanup process work across different programming languages?

Yes, the diff cleanup process works across different programming languages. It applies generically to diffs between branches or main, focusing on enforcing minimal and idiomatic edits according to existing repository conventions.

When should I avoid using automated code cleanup on my working diff?

You should avoid automated code cleanup when your working diff requires broad refactors outside the intended feature scope. The skill specifically avoids unrelated refactors and enforces minimal edits to maintain clean, auditable histories.