riot check

riot check is the shortest path from editing to useful feedback.

It exists because most development time is not spent doing full builds. It is spent making local changes and asking: “did I break the package?”

Why it matters

A toolchain without a good checking loop trains people to either:

• overbuild constantly
• ignore feedback until too late

Neither is good.

riot check is the answer to that problem. It should be fast enough to run often and accurate enough to trust.

The normal place in the workflow

A common rhythm is:

1. edit code
2. run riot check
3. if needed, run riot fix
4. once the package feels stable, run riot build

That keeps the fast loop fast and reserves the heavier loop for when it is actually needed.

What users should expect

They should expect diagnostics that are:

• package-aware
• consistent with the wider toolchain
• useful enough to act on immediately

That last point matters. A check command that is technically correct but operationally unclear is still failing the user.