lint-fix

Run linting and type checking commands and fix code errors.

Updated May 6, 2026
One-click install
npx skills add https://github.com/franzosterkamp/card2contact --skill lint-fix-franzosterkamp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint-fix
Source: https://github.com/franzosterkamp/card2contact/tree/main/.agents/skills/lint-fix
Command: npx skills add https://github.com/franzosterkamp/card2contact --skill lint-fix-franzosterkamp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates running linting and type checking tools, helping developers identify and fix code errors efficiently.

Core Features & Use Cases

  • Automated Code Style Correction: Run pnpm run lint and tsc to detect issues.
  • Error Resolution Guidance: Analyze reported errors and apply fixes automatically.
  • Use Case: A developer wants to ensure their codebase is free of lint and type errors before pushing changes; this Skill automates that process and ensures high code quality.

Quick Start

Use this skill to run the full lint pipeline on your project directory and fix any issues.

Frequently Asked Questions about lint-fix

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

FAQPage Schema
How do I automate lint and type checking fixes before pushing code changes?

Automating lint and type checking fixes involves running `pnpm run lint` and `tsc --noEmit` commands to detect code style and type errors, then applying automated corrections to ensure an error-free codebase.

What is the best way to enforce consistent coding standards in a TypeScript project?

Enforcing consistent coding standards requires executing linting and type checking tools like `tsc` to analyze the project directory, automatically correcting identified code style and type errors to improve maintainability.

Does this linting automation work with pnpm and TypeScript?

Yes, this linting automation works with pnpm and TypeScript by requiring existing scripts that run `pnpm run lint` and `tsc --noEmit` within the project directory to execute the automated error correction pipeline.

How do I run a full lint pipeline to fix code style and type errors?

Running a full lint pipeline to fix code style and type errors requires executing the configured `pnpm run lint` and `tsc --noEmit` scripts, which analyze the codebase and guide the resolution of reported errors automatically.

What do I need to set up before running automated code style correction?

Before running automated code style correction, you need a project directory configured with the necessary scripts to execute `pnpm run lint` and `tsc --noEmit` commands for identifying lint and type errors.

Why does automated code fix automation require specific lint and type check scripts?

Automated code fix automation requires specific lint and type check scripts because it depends on the `pnpm run lint` and `tsc --noEmit` commands to accurately identify code style violations and type errors before applying corrections.