Qltysh

Code quality and coverage done right

[Qltysh @qltysh]

Setting up code coverage on CI usually goes like this. You add the upload step, push, and wait for the whole test suite. One path is wrong. You fix it, push, and wait again.
Now there's a button for that. Automatic coverage setup reads your CI config and opens a draft PR with the change. You review the diff and merge it.
Here it is on a fork of rails/thor, about three minutes from click to PR.
It's on for every Qlty Cloud workspace today, tested on GitHub Actions, best effort on other CI.
https://t.co/YG5KKCeEH8

[Qltysh @qltysh]

Software teams are drowning in AI code slop. Today we're releasing SlopOne, a free research preview in the Qlty CLI. It scores maintainability with static analysis plus Jev, the new System One model from @typesafeai.

In our testing, SlopOne outperformed every available algorithm at predicting the maintainability of code.

Static analysis sees the structure of code, not its meaning. Jev answers the questions a reviewer asks, like "Would an experienced developer consider this code difficult to maintain?", cheaply and fast enough to run on every file. SlopOne learns from both.

You also get a report of maintainability over time. Select the files to clean up, click "Copy refactor prompt", and hand the fix to your coding agent.

Free. Bring your own Jev key. A historical analysis typically costs less than $1.

https://t.co/nPO0B7PEQl

[Qltysh @qltysh]

🚀 Introducing Qlty Software!

Our mission: Help developers improve Code Health—the maintainability, reliability, & security of their applications.

Let’s build the future, one line of better code at a time.

https://t.co/6153Do1h7H

[Qltysh @qltysh]

Hello, world!