
blaze
After every write of a Rust file, the new errors and warnings blaze check has for it.
- GitHub stars
- 2.4K
Install
/plugin install blaze@blazeRun it inside Claude Code after adding the marketplace with /plugin marketplace add indexable-inc/blaze.
Contents
Discovered from sourceCommands 2
Run blaze check --workspace --all-targets in the workspace root and wait for it to end.
List every error first, then every warning, each as path:line:col: level[code]: message with
blaze's help line under it, grouped by package. End with the counts and blaze's closing
blaze: ok or blaze: failed line, and the blaze check --fix hint if blaze printed one. If blaze
itself failed (no closing line, a panic, a usage error), show its last lines and say so plainly.
Run blaze why $ARGUMENTS and blaze slow in the workspace, in that order. blaze why says what
the last build recomputed and the chain of reasons for each (with an item named, why that item
reran); blaze slow says where the last build's time went, from its profile.
Then answer in a few lines, quoting their rows rather than guessing: what reran and the cause blaze
gives, the spans that took the most time with their times, and the next command blaze names
(blaze explain ...) if one would say more. If either command fails, show its last lines and say
it was blaze that failed; do not explain the build without its answer.
Hooks 2
Sponsors
Details
- Marketplace
- indexable-inc/blaze
- Source
- plugins
- Category
- Community