Jump-App

Jump-App / credo_checks

Public

A collection of opinionated Credo checks aimed at improving code quality and catching common mistakes

17
1
100% credibility
Found Apr 21, 2026 at 17 stars -- GitGems finds repos before they trend. Get early access to the next one.
Sign Up Free
AI Analysis
Elixir
AI Summary

A bundle of smart rules for the Credo code checker that helps Elixir developers write better tests, forms, and background jobs in Phoenix LiveView and Oban apps.

How It Works

1
🔍 Hear about better code helpers

While building your web app, you learn about a friendly set of tips that spot common slip-ups and make your code stronger.

2
📦 Add the helpers to your project

You easily bring in this collection of smart checks into your app's toolkit with a simple update.

3
⚙️ Turn on the checks you like

Pick which helpful rules to use, like ones for better tests or safer forms, right in your setup.

4
✨ Run the checker and see magic

Hit go, and it scans your code, lighting up spots to improve with clear, kind suggestions that feel like a helpful friend.

5
🔧 Make quick fixes

Follow the easy tips to tweak your tests, forms, and jobs, watching your app get smoother and more reliable.

✅ Enjoy cleaner, stronger code

Your app now catches mistakes early, runs tests that really matter, and feels solid and professional.

Sign up to see the full architecture

4 more

Sign Up Free

Star Growth

See how this repo grew from 17 to 17 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 credo_checks?

Jump.CredoChecks is a collection of opinionated Credo checks for Elixir projects, aimed at improving code quality and catching common mistakes in Phoenix LiveView, Oban jobs, Ecto migrations, and tests. It plugs into your existing Credo setup via a simple Hex.pm dependency, adding rules that flag issues like vacuous tests, weak assertions, or forms that won't rehydrate after deploys. Elixir teams get instant linting for Phoenix-specific pitfalls that standard Credo overlooks.

Why is it gaining traction?

These checks stand out by targeting real-world Elixir pain points—like LiveView test anti-patterns or Oban worker misconfigurations—that trip up even experienced devs, without bloating your config. The hook is their production-honed focus: they catch LLM-generated junk tests and enforce subtle best practices, like preferring text columns in Postgres migrations. Unlike generic linters, they deliver just-in-time education via clear, actionable messages.

Who should use this?

Phoenix LiveView devs writing flaky integration tests, Oban users standardizing Pro workers, or Elixir teams enforcing strict test hygiene. Ideal for mid-sized apps where migrations need auditing or docs with IEx examples must be verified via doctests. Skip if you're not on Credo or lack LiveView/Oban.

Verdict

Grab it if you're deep in Elixir/Phoenix—solid docs and Hex integration make setup trivial, despite low stars (17) and 1.0% credibility score signaling early maturity. Test coverage is strong internally, but watch for edge cases in non-standard setups.

(187 words)

Sign up to read the full AI review Sign Up Free

Similar repos coming soon.