01
It starts by itself
CI check fails. Runs in GitHub Actions or Claude Code routine.
- ↻ CI check fails
check_run.completed with conclusion failure
Red builds turned green, narrowly.
Install the Fix Errors skill and make it a habit: follow https://gethabit.dev/skills/warpdotdev/fix-errors.md
28K installs628 starsMIT licenceSource on GitHub ↗

Fix Errors
by warpdotdev · 28K installs
The skill
The fix errors skill helps developers fix compile errors, clippy and fmt failures, WASM errors and test failures in the warp Rust codebase with the narrowest useful command.
Only when you ask.
The habit
Red builds turned green, narrowly.
↻ Runs by itselfCI check fails
When does it start? How does it check its work? What does it remember?
One failed CI run per run, at most two fix rounds; full presubmit only when required.
The agent reads the full message and checks if several errors share a cause.
It fixes one error type at a time, gating WASM-only code behind local_fs when needed.
It runs the smallest useful cargo check or cargo nextest run -p for the package.
It runs the applicable clippy command, including WASM clippy for WASM errors.
It runs ./script/format once at the end and does not rerun tests after.
It writes only in its own folder and asks you before anything goes out.
Read both lists. If the left one sounds like you, the Fix Errors skill helps.
Only when you, the task or an approved spec asks for ./script/presubmit.
The skill says formatting alone needs only the formatter, not another test or clippy pass.
Copy the prompt at the top into your agent. It installs the skill from warpdotdev/common-skills and sets up the habit. Or run npx skills add warpdotdev/common-skills --skill fix-errors.
Yes. It is published under MIT. Habit is free too.
Install the Fix Errors skill and make it a habit: follow https://gethabit.dev/skills/warpdotdev/fix-errors.md
All warpdotdev skills →More code skills →
Works in
Made by warpdotdev, published under MIT. Habit links to the original and never changes it. Is this your skill?