fix-clippy
Automates and guides the resolution of Rust clippy warnings.
Install
mkdir -p .claude/skills/fix-clippy && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/1894" && unzip -o skill.zip -d .claude/skills/fix-clippy && rm skill.zipInstalls to .claude/skills/fix-clippy
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Fix all clippy lint warnings in the projectKey capabilities
- →Apply automatic fixes via make targets
- →Identify warnings using cargo clippy --tests
- →Sort and filter unique clippy warnings
- →Resolve manual code-level linting adjustments
How it works
Utilizes a two-phase cleanup where automated tools resolve standard issues followed by manual triage of deeper logical warnings.
Inputs & outputs
When to use fix-clippy
- →Cleaning up code warnings
- →Applying idiomatic rust fixes
- →Satisfying clippy standards
About this skill
Fix Clippy
Clippy issues are warnings, not errors. Never grep for error when looking for clippy issues.
Step 1: Auto-fix
Run make fix to automatically fix clippy warnings:
make fix
Step 2: Fix remaining warnings manually
Check for remaining warnings that couldn't be auto-fixed:
cargo clippy --tests 2>&1 | grep "^warning:" | sort -u
For each remaining warning, find the exact location and fix it manually.
When not to use it
- →When the issue is an actual compilation error
- →When code changes are restricted by branch policy
Prerequisites
Limitations
- →Requires knowledge of rust code logic for manual fixes
- →Limited to clippy output
How it compares
It distinguishes between auto-fixable warnings and manual interventions, preventing users from treating build errors as lints.
Compared to similar skills
fix-clippy side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| fix-clippy (this skill) | 3 | 6mo | No flags | Beginner |
| debug-cli | 1 | 8mo | Review | Intermediate |
| handling-rust-errors | 4 | 2mo | No flags | Intermediate |
| search-code | 2 | 4mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by quickwit-oss
View all by quickwit-oss →You might also like
debug-cli
antinomyhq
Use when users need to debug, modify, or extend the code-forge application's CLI commands, argument parsing, or CLI behavior. This includes adding new commands, fixing CLI bugs, updating command options, or troubleshooting CLI-related issues.
handling-rust-errors
hashintel
HASH error handling patterns using error-stack crate. Use when working with Result types, Report types, defining custom errors, propagating errors with change_context, adding context with attach, implementing Error trait, or documenting error conditions in Rust code.
search-code
JamieMason
Search for code patterns in Syncpack. Use when finding symbols, implementations, or understanding how code is used. Covers ast-grep for Rust and grep/rg for other cases.
m01-ownership
actionbook
CRITICAL: Use for ownership/borrow/lifetime issues. Triggers: E0382, E0597, E0506, E0507, E0515, E0716, E0106, value moved, borrowed value does not live long enough, cannot move out of, use of moved value, ownership, borrow, lifetime, 'a, 'static, move, clone, Copy, 所有权, 借用, 生命周期
m03-mutability
actionbook
CRITICAL: Use for mutability issues. Triggers: E0596, E0499, E0502, cannot borrow as mutable, already borrowed as immutable, mut, &mut, interior mutability, Cell, RefCell, Mutex, RwLock, 可变性, 内部可变性, 借用冲突
bisect-ssa-pass
noir-lang
Workflow for debugging SSA pass semantic preservation using the noir-ssa CLI. Use when a program's behavior changes incorrectly during the SSA pipeline - bisects passes to identify which one breaks semantics. The `pass_vs_prev` fuzzer finds such issues automatically.