skills.rest
narrative-io
narrative-ioOFFICIAL
Explore all skills by this author →
WebsiteGitHub

lint

Identify and fix linting errors in TypeScript/JavaScript projects with bun check.

Updated Jul 25, 2025
Search Tags:#typescript#refactor#code-quality#best-practices#static-analysis#lint#bun-check
One-click install
npx skills add https://github.com/narrative-io/data-collaboration-mcp --skill lint-narrative-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lint
Source: https://github.com/narrative-io/data-collaboration-mcp/tree/main/.claude/skills/lint
Command: npx skills add https://github.com/narrative-io/data-collaboration-mcp --skill lint-narrative-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of identifying and fixing linting errors in a codebase, ensuring code quality without bypassing rules.

Core Features & Use Cases

  • Automatically detect linting issues with bun check and report actionable fixes
  • Provide idiomatic fixes that preserve behavior, improve readability, and align with project standards
  • Support a repeatable workflow: identify, fix, verify, and re-check to guarantee zero warnings

Quick Start

Initiate the lint workflow by running bun check, review all issues, and apply idiomatic fixes until the project passes.

Frequently Asked Questions about lint

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

FAQPage Schema
How do I fix TypeScript lint errors without suppressing rules?▼

TypeScript lint errors can be fixed without suppressing rules by applying idiomatic code adjustments, adding proper type annotations, and formatting the codebase, then verifying the results with a deterministic check to ensure zero warnings.

What is the best way to automate static analysis fixes in a TypeScript project?▼

The best way to automate static analysis fixes is to use a repeatable workflow that identifies issues, applies idiomatic TypeScript fixes, and verifies the codebase with a deterministic check until all errors and warnings are resolved.

How does bun check work for verifying code quality fixes?▼

bun check works for verifying code quality by running a deterministic validation process across the codebase. It identifies linting issues and confirms whether the applied idiomatic fixes have successfully resolved all errors and warnings.

Can I use this approach to refactor code for best practices without changing behavior?▼

Yes, you can refactor code for best practices without changing behavior by applying idiomatic TypeScript and JavaScript fixes. This process improves readability and aligns with project standards while preserving the original functionality.

Why do my lint fixes still show warnings after I run static analysis?▼

Lint fixes may still show warnings after static analysis if the changes are incomplete or lack proper type annotations. A repeatable identify, fix, and verify workflow is needed to apply idiomatic solutions and re-run checks until zero warnings remain.

Related Skills

Explore More Software Engineering Skills→
Asymmetric-alAsymmetric-al
417

lint-and-validate

Lint and validate Node.js, TypeScript, and Python code for syntax and standards.

Official
Intermediate
cartridge-ggcartridge-gg
80

pre-commit-check

Run Husky pre-commit hooks for format, lint, and test checks.

Official
Intermediate
Spectaculous-CodeSpectaculous-Code

lint-fixer

Analyze and resolve linting and formatting issues in TypeScript and React codebases using Biome.

Official
Intermediate
framerslabframerslab

code-safety

Scan LLM-generated code for injection, XSS, and security vulnerabilities.

Official
Intermediate