lint-formatting

Identify and apply language-specific linting, formatting, and static type-checking commands.

9|Updated Dec 21, 2016
One-click install
npx skills add https://github.com/ysoftman/myenv --skill lint-formatting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint-formatting
Source: https://github.com/ysoftman/myenv/tree/main/.claude/skills/lint-formatting
Command: npx skills add https://github.com/ysoftman/myenv --skill lint-formatting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Linting, formatting, and static type-checking across language ecosystems can be time-consuming and error-prone. This Skill aggregates language-specific commands into a single, maintainable reference to help engineers enforce consistency and speed up code quality workflows.

Core Features & Use Cases

  • Cross-language coverage for JavaScript/TypeScript, Go, Rust, Python, HTML, Shell, and Markdown workflows.
  • Detailed variants for check-only, fix-only, and combined workflows to fit CI, pre-commit, or local development.
  • Real-world scenario: quickly auditing a mixed repository and applying style and type fixes across multiple packages.

Quick Start

Run the lint-formatting reference to identify and apply fixes across your codebase.

Frequently Asked Questions about lint-formatting

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

FAQPage Schema
How do I run lint and format checks across multiple languages in a monorepo?

Lint and format checks across multiple languages are unified by routing JavaScript, Go, Rust, Python, and Shell files to Biome, golangci-lint, rustfmt, ruff, and shfmt. This provides consistent code quality results across mixed repository workflows in a single pass.

Can I apply lint fixes and type-checking separately or do they have to run together?

Lint fixes and type-checking can run separately using check-only, fix-only, or mixed-operation variants. This flexibility allows you to apply automated style fixes locally via ruff or Biome while isolating pyright type-checking results for CI pipelines.

What is the best way to enforce consistent formatting for Shell and Markdown files?

Consistent formatting for Shell and Markdown files is enforced by applying shfmt and Prettier. Using these defined tools ensures that shell scripts and documentation maintain uniform indentation and style across all project contributions.

Does this linting workflow support Python static analysis with ruff and pyright?

Python static analysis is fully supported through ruff for linting and formatting alongside pyright for type-checking. This combination delivers comprehensive static analysis by identifying style violations and type errors before runtime.

How do I configure golangci-lint and rustfmt for a mixed Go and Rust project?

Configuring golangci-lint and rustfmt for mixed Go and Rust projects is handled through configuration-aware guidance. This ensures both tools respect your existing project settings to deliver accurate linting and formatting without overriding custom rules.

Why do I need a unified command reference for static analysis and formatting?

A unified reference for static analysis and formatting is needed to eliminate the friction of remembering individual tool syntax across ecosystems. It aggregates language-specific commands to help engineers speed up code quality workflows and maintain consistency.