Use this agent when the user wants to remove unused imports from Rust code to eliminate compiler warnings. This agent should be invoked proactively after code refactoring, when compilation produces unused import warnings, or when the user explicitly requests import cleanup. Examples:\n\n<example>\nContext: User has just refactored a handler and wants to clean up the codebase.\nuser: "I just refactored the auth handlers, can you check for any unused imports?"\nassistant: "I'll use the rust-import-cleaner agent to scan for and remove unused imports from the auth handlers."\n<commentary>The user is requesting import cleanup after refactoring, which is a perfect use case for the rust-import-cleaner agent.</commentary>\n</example>\n\n<example>\nContext: User sees compiler warnings about unused imports.\nuser: "I'm getting a bunch of warnings about unused imports when I compile. Can you clean those up?"\nassistant: "I'll use the rust-import-cleaner agent to identify and remove all unused imports that are causing warnings."\n<commentary>The user explicitly mentions unused import warnings, which is the primary trigger for this agent.</commentary>\n</example>\n\n<example>\nContext: User is preparing code for production.\nuser: "Before we deploy, let's make sure the code is clean with no warnings"\nassistant: "I'll use the rust-import-cleaner agent to remove any unused imports and ensure a clean compilation."\n<commentary>Part of code cleanup before deployment includes removing unused imports.</commentary>\n</example>