# Extensible code linter

**URL:** <https://forum.crystal-lang.org/t/extensible-code-linter/8972>\
**Category:** Community\
**Created:** [June 5, 2026, 9:49pm UTC](https://forum.crystal-lang.org/t/extensible-code-linter/8972 "2026-06-05T21:49:35Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Xen](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.crystal-lang.org/xen/32/2288_2.png) [@Xen](https://forum.crystal-lang.org/u/Xen)\
**Post date:** [June 5, 2026, 9:49pm UTC](https://forum.crystal-lang.org/t/extensible-code-linter/8972/1 "2026-06-05T21:49:35Z")

</div>

[Gojko Adžić on the Modern Software Engineering channel](https://www.youtube.com/watch?v=hgZj02hPZuw) makes a good point that markdown prayers doesn’t help when your enthusiastic intern (LLM) shows up at work drunk. You need stricter guardrails.

And I rapidly developed an interest in this topic when I caught Gemini sneaking in a `uninitialized` var (why? I have no idea).

In JavaScript/PHP/others it’s just a matter of asking the LLM to write a rule for the linter you’re already using, and add that to the project.

But that’s a bit more complicated in Crystal land, `ameba` is nice, but not particularly extensible, it seems. Of course my particular issue can be caught with `rg`, but it would be nice if things was a bit more integrated.

Thoughts? Any tools I’ve not yet discovered?

---

<div class="post-metadata">

**Author:** ![Blacksmoke16](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.crystal-lang.org/blacksmoke16/32/1241_2.png) [@Blacksmoke16](https://forum.crystal-lang.org/u/Blacksmoke16)\
**Post date:** [June 5, 2026, 10:19pm UTC](https://forum.crystal-lang.org/t/extensible-code-linter/8972/2 "2026-06-05T22:19:58Z")

</div>

IIRC ameba had this in its `bin/`:

```crystal
#!/usr/bin/env crystal

# Require ameba extensions here which are added as project dependencies.
# Example:
#
# require "ameba-performance"

# Require ameba cli which starts the inspection.
require "ameba/cli"

```

But does mean you’d have to have a local binary to require extensions into/use for your project. Versus like just picking up extensions dynamically when you run it. But that may be your best bet in the meantime.

---

<div class="post-metadata">

**Author:** ![Xen](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.crystal-lang.org/xen/32/2288_2.png) [@Xen](https://forum.crystal-lang.org/u/Xen)\
**Post date:** [June 5, 2026, 11:35pm UTC](https://forum.crystal-lang.org/t/extensible-code-linter/8972/3 "2026-06-05T23:35:07Z")

</div>

Oh, nice, something to work with. Thanks.

---

<div class="post-metadata">

**Author:** ![Sija](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.crystal-lang.org/sija/32/737_2.png) [@Sija](https://forum.crystal-lang.org/u/Sija)\
**Post date:** [June 7, 2026, 9:03am UTC](https://forum.crystal-lang.org/t/extensible-code-linter/8972/4 "2026-06-07T09:03:54Z")

</div>

A good example of extending Ameba in action can be seen here: [GitHub - toddsundsted/ktistec: ActivityPub (https://www.w3.org/TR/activitypub/) server for individual users and small groups. · GitHub](https://github.com/toddsundsted/ktistec)

---

<div class="post-metadata">

**Author:** ![Xen](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.crystal-lang.org/xen/32/2288_2.png) [@Xen](https://forum.crystal-lang.org/u/Xen)\
**Post date:** [June 7, 2026, 12:06pm UTC](https://forum.crystal-lang.org/t/extensible-code-linter/8972/5 "2026-06-07T12:06:42Z")

</div>

Oh, most excellent, I must study.
