Lint

What it does

The Lint skill checks code quality and formatting before committing changes. It analyzes your codebase for lint errors and identifies any formatting issues that need to be addressed. This helps ensure a consistent coding style and catches potential problems early in the development process, improving overall code maintainability. The skill uses make commands and cargo for Rust-specific checks.

When to use it

• Before committing changes to a repository.
• To enforce consistent code formatting within a project.
• When identifying and resolving linting errors.
• As part of a continuous integration/continuous delivery (CI/CD) pipeline.

Key capabilities

• Runs lint checks for potential errors.
• Checks code formatting according to defined standards.
• Provides instructions on fixing common Clippy warnings and errors.
• Includes guidance on adding missing license headers.
• Supports Rust-specific linting using cargo clippy.

Example prompts

• "Run a lint check on the current codebase."
• "Check the formatting of my code."
• "Fix any formatting issues I have."

Tips & gotchas

• The skill relies on make commands and cargo, so these tools must be available in your environment.
• If Clippy reports warnings or errors, it's important to fix them before proceeding.
• For Rust-only linting, navigate to the src/redisearch_rs directory and run cargo clippy --all-targets --all-features.