lint-fix

Detect project linting tools and assemble a zero-error execution pipeline.

3|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/rshade/agent-skills --skill lint-fix-rshade
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint-fix
Source: https://github.com/rshade/agent-skills/tree/main/skills/lint-fix
Command: npx skills add https://github.com/rshade/agent-skills --skill lint-fix-rshade

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detect project linting and validation tools, build an execution pipeline, run all tools to zero errors, and fix issues using an atomic fix protocol.

Core Features & Use Cases

  • Tool detection: scan for Makefile targets, package.json scripts, go.mod, pyproject.toml, and standalone configs to surface available tooling.
  • Pipeline orchestration: automatically order steps (generation, formatting, linting, type checking, validation, testing, building) and present the plan before running.
  • Atomic fixes & verification: apply one issue fix at a time, re-run the failing command, and verify no new issues appear.

Quick Start

Scan your project for tooling, build an ordered pipeline, and fix issues one at a time until zero errors are achieved.

Frequently Asked Questions about lint-fix

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

FAQPage Schema
How do I automate linting and fix code quality issues across different project types?

You can automate linting by detecting project tools from configurations like Makefile, package.json, go.mod, and pyproject.toml, then assembling an ordered pipeline to run formatting, linting, type checking, and testing to zero errors.

How does an atomic fix protocol resolve linting errors?

An atomic fix protocol applies one issue fix at a time, re-runs the failing command, and verifies that no new issues appear, ensuring code quality is maintained without introducing regressions during validation.

Can I use this to build an execution pipeline for standalone linting configs?

Yes, the tool detection scans for standalone configurations alongside ecosystem files like Makefile and package.json to surface available tooling and orchestrate a complete validation pipeline.

What is the best way to coordinate generation, formatting, and type checking in one run?

Pipeline orchestration automatically orders steps including generation, formatting, linting, type checking, validation, testing, and building, presenting the execution plan before running to ensure coordinated code quality checks.

Does this automated validation tool support projects with a pyproject.toml file?

Yes, it detects pyproject.toml files along with Makefile targets, package.json scripts, and go.mod files to identify project tooling and build the appropriate zero-error execution pipeline.

Why should I run linting and validation tools one fix at a time instead of batch fixing?

Applying fixes atomically one at a time and re-running the failing command prevents new issues from appearing, ensuring that each fix is verified and does not introduce new errors into the pipeline.