auto-linter

Format changed Rust files with cargo fmt and lint them with cargo clippy.

5|Updated Nov 26, 2025
One-click install
npx skills add https://github.com/EffortlessMetrics/demo-swarm --skill auto-linter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-linter
Source: https://github.com/EffortlessMetrics/demo-swarm/tree/main/.claude/skills/auto-linter
Command: npx skills add https://github.com/EffortlessMetrics/demo-swarm --skill auto-linter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the tedious manual work of code formatting and linting, which often leads to inconsistent codebases, developer friction, and wasted time. It ensures your code adheres to standards automatically.

Core Features & Use Cases

  • Automated Formatting: Applies cargo fmt to ensure consistent Rust code style across your project, modifying files safely.
  • Linting & Reporting: Runs cargo clippy to identify potential code quality issues, providing a clear summary of warnings and errors without auto-applying semantic fixes.
  • Targeted Efficiency: Prioritizes running on changed files (git diff) for faster feedback, falling back to a full repository scan when necessary.
  • Use Case: Integrate this Skill into your CI/CD pipeline or a "Build" flow to automatically format all new Rust code and report any linting issues before merging, ensuring high code quality and consistency without manual intervention.

Quick Start

Run the auto-linter skill to format and lint all changed Rust files in the current branch, saving the output to 'lint_output.log' and a summary to 'lint_summary.md'.

Frequently Asked Questions about auto-linter

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

FAQPage Schema
How do I automate code formatting and linting for Rust projects?

Automate code formatting and linting by running cargo fmt for style consistency and cargo clippy for quality checks. This Skill applies both tools to changed files detected via git diff, saving results to lint_output.log and lint_summary.md, then reports warning and error counts.

Can I run linting and formatting only on changed files in my Rust repository?

Yes. This Skill targets modified files using git diff against origin/main for faster feedback, then falls back to scanning the repository root if diff information is unavailable, ensuring efficient CI/CD integration.

What's the best way to enforce consistent code style before merging Rust PRs?

Integrate this Skill into your CI/CD pipeline or Build flow to automatically format all new Rust code and report linting issues before merge. Formatting modifies files safely while linting reports findings without applying semantic changes.

Does this tool modify my Rust source files or only report issues?

Formatting via cargo fmt modifies files to ensure consistent style, while linting via cargo clippy reports warnings and errors without applying semantic fixes or removing tests, giving you control over which changes to accept.

How do I integrate Rust code quality checks into my development workflow?

Use this Skill in your Git workflow to detect changed Rust files, apply formatting standards, and generate linting summaries. Outputs are logged to lint_output.log and lint_summary.md for review and tracking.

What happens if git diff information isn't available in my repository?

The Skill falls back to operating at the repository root, scanning all Rust files instead of just changed ones, ensuring linting and formatting still complete even when branch comparison data is unavailable.