fix-lint

Run the lint:fix workflow to incrementally fix frontend lint failures.

123|29|Updated Aug 21, 2021
One-click install
npx skills add https://github.com/codecrafters-io/frontend --skill fix-lint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-lint
Source: https://github.com/codecrafters-io/frontend/tree/main/.cursor/skills/fix-lint
Command: npx skills add https://github.com/codecrafters-io/frontend --skill fix-lint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the repetitive process of addressing frontend lint failures by running fixes iteratively until the codebase adheres to the project's lint rules.

Core Features & Use Cases

  • Incremental lint remediation: apply fixes one issue at a time to preserve code stability.
  • Automated validation: re-run lint checks after each fix to verify progress.
  • Use Case: when a team wants to rapidly reduce lint warnings across a large frontend repository.

Quick Start

Run the lint-fix command to start auto-remediation and monitor the output for confirmed fixes.

Frequently Asked Questions about fix-lint

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

FAQPage Schema
How do I automatically fix frontend lint issues in a large repository?

To automatically fix frontend lint issues, this Skill runs the project's lint-fix workflow iteratively. It identifies lint failures within the frontend repository and applies fixes incrementally, rechecking after each change to ensure code stability.

Do I need bun installed to run automated lint remediation?

Yes, you need the bun tool installed to run automated lint remediation. The Skill requires bun and the project's available lint script to execute fixes and validate outcomes within your frontend repository.

What is incremental lint remediation and how does it preserve code stability?

Incremental lint remediation applies fixes one issue at a time rather than all at once. After each individual fix, the Skill re-runs lint checks to validate progress, ensuring code stability throughout the automated process.

Can I use this automated lint fix workflow to reduce warnings across a large codebase?

Yes, you can use this automated lint fix workflow to reduce warnings across a large codebase. It iteratively runs the lint:fix command, applying fixes and validating outcomes until the codebase adheres to lint rules.

What happens if the lint script is not available in my frontend project?

If the project's lint script is not available, the automated lint fix cannot execute. The Skill explicitly requires the project's lint script to be present to run fixes and validate outcomes.

Why does the automated lint fix recheck the code after every change?

The automated lint fix rechecks the code after every change to verify progress and prevent regressions. This incremental validation ensures each applied fix successfully resolves the issue without introducing new lint failures.