Agent skill

Slop

by jellydn in jellydn/my-ai-tools

Remove AI-generated code slop from git diffs to maintain code quality

MITAuto-check passedDevelopment

Install Slop

skills CLI
$ npx skills add jellydn/my-ai-tools --skill slop -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jellydn/my-ai-tools slop --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jellydn/my-ai-tools.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/slop .claude/skills/slop && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
slop
GitHub stars
123
Token cost
~1.1k tokens
SKILL.md length
494 words
Files
1
Skills in repo
33
Repo updated
First seen
Licence
MIT

At a glance

Remove AI-generated code slop from git diffs to maintain code quality

  • Works in 8 steps: Preserve Functionality → Apply Project Standards → Enhance Clarity → …
  • Tasks that involve Code quality
  • SKILL.md covers Usage, What is AI Code Slop?, Core Principles and Process, plus 2 more sections
  • Calls git and npm

What it does

Slop is an agent skill from jellydn/my-ai-tools. Remove AI-generated code slop from git diffs to maintain code quality

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: cline, claude, opencode, amp, codex, gemini, cursor, pi

It sits in Development, covering Code quality. It works with Git. The repository describes itself as: Comprehensive configuration management for AI coding tools - Replicate my complete setup for Claude Code, OpenCode, Amp, Li, Codex and Claude Code Switch with custom… The licence is MIT.

When your agent uses it

  • Tasks that involve Code quality

Example prompts

  • “/slop”

Requirements

  • Compatibility (from SKILL.md): cline, claude, opencode, amp, codex, gemini, cursor, pi

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. Preserve Functionality
  2. Apply Project Standards
  3. Enhance Clarity
  4. Maintain Balance
  5. Get the diff
  6. Review each changed file
  7. Remove slop and refine
  8. Verify

What it can do on your machine

Read from SKILL.md and the folder at commit 62c9227. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git and npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    cline, claude, opencode, amp, codex, gemini, cursor, pi

    From compatibility in the SKILL.md frontmatter.

Context cost

Slop loads about 1.1k tokens when it runs. Until then it costs about 19 tokens; SKILL.md has 494 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~19
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jellydn/my-ai-tools at commit 62c9227, republished under its MIT licence (© jellydn). 494 words, ~1,081 tokens.

Download SKILL.mdSave it as .claude/skills/slop/SKILL.md (or your agent's skills folder).
name
slop
description
Remove AI-generated code slop from git diffs to maintain code quality
compatibility
cline, claude, opencode, amp, codex, gemini, cursor, pi
license
MIT
hint
Use when cleaning up AI-generated code slop in git diffs
user-invocable
true
metadata.audience
all
metadata.workflow
code-quality

Remove AI Code Slop

Check the diff against a branch and remove all AI-generated slop introduced in this branch. Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality.

Usage

/slop [branch-name]

  • If no branch is provided, compare against main: /slop main

What is AI Code Slop?

This includes:

  • Extra comments that a human wouldn't add or is inconsistent with the rest of the file
  • Extra defensive checks or try/catch blocks that are abnormal for that area of the codebase
  • Casts to any to get around type issues
  • Any other style that is inconsistent with the file

Core Principles

1. Preserve Functionality

Never change what the code does - only how it does it. All original features, outputs, and behaviors must remain intact.

2. Apply Project Standards

Follow the established coding standards from @CLAUDE.md or conventions:

  • Use proper import sorting and file organization
  • Follow language-specific patterns (ES modules, proper TypeScript types, etc.)
  • Maintain consistent naming conventions
  • Use proper error handling patterns
3. Enhance Clarity

Simplify code structure by:

  • Reducing unnecessary complexity and nesting
  • Eliminating redundant code and abstractions
  • Improving readability through clear variable and function names
  • Consolidating related logic
  • Removing unnecessary comments that describe obvious code
  • IMPORTANT: Use switch statements or if/else chains over nested ternary operators
  • Choose clarity over brevity - explicit code is often better than overly compact code
4. Maintain Balance

Preserve necessary complexity — over-simplification can:

  • Reduce code clarity or maintainability
  • Create overly clever solutions that are hard to understand
  • Combine too many concerns into single functions
  • Remove helpful abstractions that improve code organization
  • Prioritize "fewer lines" over readability

Process

1. Get the diff
bash
# Compare against main branch
git diff main...HEAD --stat

# Or against specific branch
git diff $1 --stat
2. Review each changed file

For each changed file:

  • Read the current content
  • Compare with original (before changes)
  • Identify AI-generated slop patterns
  • Check for opportunities to improve elegance and consistency
Show full SKILL.md (196 more words)Show less
3. Remove slop and refine
  • Remove unnecessary comments
  • Simplify overly defensive code
  • Remove any casts where possible
  • Restore natural code style
  • Apply project-specific best practices
  • Ensure all functionality remains unchanged
4. Verify
bash
# Show remaining changes
git diff --stat

# Check tests still pass
npm test

Common Slop Patterns

  1. Over-commenting: Comments explaining obvious code
  2. Verbose error handling: Try/catch blocks where not needed
  3. Unnecessary type casts: x as any to bypass TypeScript
  4. Defensive programming: Checks for already-validated inputs
  5. Redundant validation: Duplicate null/undefined checks
  6. Nested ternaries: Complex nested ternary operators
  7. Overly compact code: Dense one-liners that sacrifice readability

Refinement Guidelines

When refining code:

  1. Identify the modified sections - Only refine code that changed in the diff
  2. Analyze for improvement opportunities - Look for ways to enhance elegance and consistency
  3. Apply project standards - Follow established conventions and patterns
  4. Preserve functionality - Ensure behavior remains unchanged
  5. Verify improvements - The refined code should be simpler and more maintainable
  6. Document significant changes - Only document changes that affect understanding
Code Style Preferences
  • Prefer explicit over compact - readable code beats clever code
  • Use descriptive names - clarity over brevity
  • Flatten deep nesting with early returns and guard clauses
  • Remove redundant code - eliminate duplicates
  • Use language-appropriate patterns - follow idiomatic practices

© jellydn, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/slop of jellydn/my-ai-tools.

Open the folder on GitHubat commit 62c9227

Compare with similar skills

Slop next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Slop compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Slop this skilljellydn/my-ai-tools123—~1.1kAutomated safety check: PassMIT
Qt C++ Code Reviewx-tools-author/x-tools1.1k2 repos~4.3kAutomated safety check: PassBSD-3-Clause
Skill Doctorwarpdotdev/common-skills6102 repos~2.6kAutomated safety check: PassMIT
Ponytail Debt LedgerDietrichGebert/ponytail160k—~453Automated safety check: PassMIT
Worktrunk CLI Output Rulesmax-sixty/worktrunk9.2k—~12kAutomated safety check: PassCustom licence
Adversarial Reviewer302ai/302-AI-Studio1321 repos~3kAutomated safety check: PassMIT

Similar skills

  • Qt C++ Code Review

    x-tools-author/x-tools

    Read-only review of Qt6 C++ code that combines a deterministic lint script with six parallel analysis agents and reports only high-confidence issues.

    1.1k GitHub starsUsed in 2 repos~4.3k tokens
    DevelopmentAuto-check passed
  • Skill Doctor

    warpdotdev/common-skills

    Grades agent skills by scoring agent conversations for efficiency, code quality, procedure compliance, and verbosity, then drafts concrete skill edits and a shareable report.

    610 GitHub starsUsed in 2 repos~2.6k tokens
    DevelopmentAuto-check passed
  • Ponytail Debt Ledger

    DietrichGebert/ponytail

    Collects every ponytail: comment in a codebase into one debt ledger, flags shortcuts with no upgrade trigger and reports without changing any files.

    160k GitHub stars~453 tokensUpdated today
    DevelopmentAuto-check passed
  • Worktrunk CLI Output Rules

    max-sixty/worktrunk

    CLI output standards for worktrunk: message functions, ANSI color nesting and the shell integration that changes directory after the wt command exits.

    9.2k GitHub stars~12k tokensUpdated today
    DevelopmentAuto-check passed
  • Adversarial Reviewer

    302ai/302-AI-Studio

    Adversarial code review that breaks the self-review monoculture.

    132 GitHub starsUsed in 1 repo~3k tokens
    DevelopmentAuto-check passed
  • WebRTC Include Cleaner

    webrtc-sdk/webrtc

    Runs the WebRTC include-cleaner tool to add missing and remove unused C++ include directives before uploading a CL or after refactoring.

    446 GitHub starsUsed in 1 repo~545 tokens
    DevelopmentAuto-check passed

More from jellydn/my-ai-tools

All 33 skills in this repo
  • Babysit PR

    jellydn/my-ai-tools

    A skill your agent uses when monitoring an open GitHub PR for CI failures, review feedback, mergeability, and safe retries or fixes.

    123 GitHub stars~4.1k tokensUpdated today
    Auto-check passed
  • Visual PR

    jellydn/my-ai-tools

    Posts a concise visual outline as a GitHub pull request comment.

    123 GitHub stars~764 tokensUpdated today
    Auto-check passed
  • Qmd Knowledge

    jellydn/my-ai-tools

    Manage project knowledge with qmd — captures learnings, decisions, and conventions

    123 GitHub stars~2.1k tokensUpdated today
    Auto-check passed
  • Prd

    jellydn/my-ai-tools

    Generate Product Requirements Documents from feature ideas — plans specs and requirements

    123 GitHub starsUsed in 4 repos~1.8k tokens
    Auto-check passed
  • Capability Experiments

    jellydn/my-ai-tools

    Build an interactive report or experiment when the user asks to explore model capabilities.

    123 GitHub stars~2k tokensUpdated today
    Auto-check passed
  • PR Review

    jellydn/my-ai-tools

    Fix PR review comments by implementing requested changes. An agent skill from jellydn/my-ai-tools.

    123 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Slop

What does Slop do?

Remove AI-generated code slop from git diffs to maintain code quality. Slop is an agent skill from jellydn/my-ai-tools.

When should I use Slop?

Slop fits situations like: tasks that involve Code quality.

How do I install Slop in Claude Code?

Run `npx skills add jellydn/my-ai-tools --skill slop -a claude-code`. Or copy the skill folder (skills/slop in jellydn/my-ai-tools) into .claude/skills/slop in your project. Claude Code loads it when a task matches its description.

How do I install Slop in Codex?

Run `npx skills add jellydn/my-ai-tools --skill slop -a codex`. Or copy the skill folder (skills/slop in jellydn/my-ai-tools) into .agents/skills/slop in your project. Codex loads it when a task matches its description.

Can I use Slop in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jellydn/my-ai-tools --skill slop -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/slop, .gemini/skills/slop, .github/skills/slop and .opencode/skills/slop in your project.

What does Slop need to run?

Going by SKILL.md and its folder, Slop needs the command-line tools its instructions call (git and npm). Compatibility (from SKILL.md): cline, claude, opencode, amp, codex, gemini, cursor, pi.

Does Slop access the network?

SKILL.md contains no URLs. Its commands use git and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Slop safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Slop use?

Slop is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Slop use?

About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Slop?

Skills that share tags, products or a category with Slop: Qt C++ Code Review (x-tools-author/x-tools, 1.1k stars), Skill Doctor (warpdotdev/common-skills, 610 stars), Ponytail Debt Ledger (DietrichGebert/ponytail, 160k stars) and Worktrunk CLI Output Rules (max-sixty/worktrunk, 9.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Slop?

jellydn (a GitHub user) maintains it in jellydn/my-ai-tools, which has 123 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 10, 2026.

Source: jellydn/my-ai-tools on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.