dannote

dannote / ex_slop

Public

Credo checks that catch AI-generated code slop in Elixir

10
0
100% credibility
Found Mar 08, 2026 at 10 stars -- GitGems finds repos before they trend. Get early access to the next one.
Sign Up Free
AI Analysis
Elixir
AI Summary

ExSlop adds specialized checks to the Credo code analyzer for Elixir to detect and flag common low-quality patterns typical of AI-generated code.

How It Works

1
🔍 Discover ExSlop

You hear about a helpful tool that spots messy patterns in code often made by AI writing helpers, making your project cleaner.

2
➕ Add to your project

You easily include this tool in your coding workspace so it can watch over your work.

3
⭐ Pick your rules

You choose which specific tips for better code you want the tool to check for, like a custom cleaning list.

4
▶️ Run the checker

With one simple action, you scan your entire project to find any sloppy spots.

5
💡 See suggestions

The tool kindly points out places to improve, explaining why each one matters in plain words.

6
✏️ Make fixes

You quickly tweak those spots following the easy advice, feeling your code get smoother.

🎉 Clean code achieved

Your project now runs beautifully with professional-quality code, free of AI slop!

Sign up to see the full architecture

5 more

Sign Up Free

Star Growth

See how this repo grew from 10 to 10 stars Sign Up Free
Repurpose This Repo

Repurpose is a Pro feature

Generate ready-to-use prompts for X threads, LinkedIn posts, blog posts, YouTube scripts, and more -- with full repo context baked in.

Unlock Repurpose
AI-Generated Review

What is ex_slop?

Ex_slop adds 18 specialized checks to Credo for Elixir projects, designed to catch ai-generated code slop like blanket rescues, narrator docs, obvious comments, and anti-idiomatic Enum patterns. It spots LLM hallmarks that experienced Elixir devs avoid, such as N+1 queries in Enum.map or try/rescue around safe functions. Install as a dev dependency via mix.exs, then cherry-pick checks into your .credo.exs for github credo elixir workflows.

Why is it gaining traction?

Unlike standard Credo, which skips doc content and Ecto pitfalls, ex_slop targets ai-generated code patterns verbatim—think repo all then filter or identity passthroughs that bloat pipelines. Devs notice fewer cargo-culted Phoenix docs and swallowed exceptions right away, cleaning up Copilot or ChatGPT outputs without false positives. It's a lightweight Credo extension with zero runtime cost, perfect for CI gates on slippery slope ex of low-effort AI code.

Who should use this?

Elixir backend teams reviewing PRs with AI-assisted code, especially Phoenix or Ecto-heavy apps prone to query_in_enum_map or genserver_as_kv_store smells. Maintainers of open-source repos hit by contributor-generated slop, or leads enforcing code quality amid tool adoption. Skip if you're not using Credo or AI generators.

Verdict

Grab it for Elixir + AI workflows—solid docs and dogfooding task make setup trivial, despite 10 stars and 1.0% credibility score signaling early maturity. Test a subset of checks first; it'll pay off catching zero slope ex boilerplate before it spreads.

(178 words)

Sign up to read the full AI review Sign Up Free

Similar repos coming soon.