sbcli VS lisp-critic

But you don't have syntax highlighting :( On errors, the debugger looks arcane… cl-repl or sbcli might help. With sbcli, you even don't have the interactive debugger, only the stacktrace. It's easier for beginners (or for quick development). They are based on readline and do some things well (match parenthesis, multiline input for cl-repl).

SLIME extension for Lisp Critic.

If you really decide to dig into Common Lisp (it's not everybody's cup of tea), check this linter as well: https://github.com/g000001/lisp-critic , or this wrapper over Lisp Critic which can work very well in your CI/CD pipelines if you use them: https://github.com/40ants/40ants-critic .

Without Lem, how do you edit files? We need to edit and load files in the REPL. magic-ed could help. What if before loading the file, we added some style criticisms? The lisp-critic is waiting to be adopted and expanded (while colisper has too simple rules).

https://github.com/g000001/lisp-critic for "linting". Formatting is usually done via emacs but I am sure something just not anything I could recommend off the top of my head. As far as building and stuff via the cli Roswell exists but for most lisp development it's done via the repl.

You can find examples here: https://github.com/g000001/lisp-critic (lisp-rules.lisp) and to a smaller extent, here: https://github.com/vindarel/colisper (src/catalogue directory). The lisp-critic is available by default on this custom readline REPL: https://ciel-lang.github.io/CIEL/#/repl?id=friendly-lisp-critic so it can be tried at the terminal (in conjunction with the %edit command). It would be nice if it had better editor integration though. (it shouldn't be too hard, there's one function (critique-file pathname) to call on a file).

Maybe lisp-critic? It's in quicklisp.