fix-errors

Diagnose and fix Rust compilation, clippy, formatting, and test failures in the warp codebase.

2|Updated May 9, 2026
One-click install
npx skills add https://github.com/Manuel-Gartenkrot-Casal/AfterDrive_Intelligence --skill fix-errors-manuel-gartenkrot-casal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fix-errors
Source: https://github.com/Manuel-Gartenkrot-Casal/AfterDrive_Intelligence/tree/main/.agents/skills/fix-errors
Command: npx skills add https://github.com/Manuel-Gartenkrot-Casal/AfterDrive_Intelligence --skill fix-errors-manuel-gartenkrot-casal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Rust development in the warp codebase often stalls on compilation errors, clippy warnings, formatting violations, WASM-specific build failures, and failing tests, and developers need a systematic way to resolve them before opening a pull request. ## Core Features & Use Cases - Presubmit Orchestration: Run the full presubmit suite (formatting, linting, tests) with a single script, or execute individual checks like cargo fmt, clippy, and nextest when debugging specific issues. - Error Pattern Catalog: Provides concrete fixes for common error types including unused imports, type mismatches, struct field changes, function signature changes, and enum variant updates. - WASM-Specific Guidance: Explains how to gate filesystem-dependent code and tests behind the local_fs feature flag to resolve wasm32-unknown-unknown target errors. - Use Case: A developer hits a clippy failure and a broken test after refactoring a struct. They follow the skill to fix the struct initialization sites, run targeted nextest filters, and verify everything with the presubmit script before opening their PR. ## Quick Start Ask the assistant to fix the current cargo build or clippy errors in the warp workspace and verify the fix by running the presubmit checks.

Frequently Asked Questions about fix-errors

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix Rust compilation errors in the warp codebase?▼

Read the full compiler error to identify the root cause, then apply the matching fix pattern such as removing unused imports, correcting type mismatches with .as_str() or .to_string(), or updating struct construction sites. Verify with cargo check before running broader checks.

How do I run a single Rust test with cargo nextest?▼

Run cargo nextest run -p <package_name> for one package, or add -E 'test(<substring>)' to filter by test name. Use --nocapture to see printed output during the test run.

Why do WASM builds fail with filesystem errors in Rust?▼

The wasm32-unknown-unknown target does not support filesystem operations, so any code using filesystem APIs must be gated behind the local_fs feature flag. Tests need #[cfg(feature = "local_fs")] and dead code can use #[cfg_attr(not(feature = "local_fs"), allow(dead_code))].

What checks run before opening a pull request in warp?▼

Run ./script/presubmit, which executes cargo fmt, workspace clippy with warnings denied, WASM clippy, clang-format for Objective-C/C/C++ files, and the full nextest suite. All checks must pass before opening or updating a PR.

How do I fix clippy warnings treated as errors in CI?▼

Run cargo clippy --workspace --all-targets --all-features --tests -- -D warnings locally to reproduce the failure. Address each warning individually, then rerun clippy and cargo fmt before pushing.