lint

Automate linting and formatting across a project with safe fixes.

1.0k|92|Updated May 22, 2026
One-click install
npx skills add https://github.com/open-gsd/gsd-pi --skill lint-open-gsd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint
Source: https://github.com/open-gsd/gsd-pi/tree/main/src/resources/skills/lint
Command: npx skills add https://github.com/open-gsd/gsd-pi --skill lint-open-gsd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintain code quality by automatically linting and formatting across a project, reducing manual review time and drift.

Core Features & Use Cases

  • Detects and fixes code style issues using project-configured linters and formatters.
  • Supports multiple ecosystems (JavaScript/TypeScript, Python, Rust, Go, etc.) through configuration files.
  • Use Case: A team wants consistent code style across a large monorepo; this Skill runs the appropriate tooling to enforce standards and auto-fix where safe.

Quick Start

Lint the target files or the entire project and apply safe fixes with the --fix flag.

Frequently Asked Questions about lint

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

FAQPage Schema
How do I lint and format code across my entire project automatically?

To lint and format code across a project, this Skill detects the appropriate tooling from your configuration and applies checks to the current working tree or a specified path. It respects project configuration and reports results clearly.

Can I auto-fix code style issues using my existing eslint and prettier setup?

Yes, you can auto-fix code style issues by running the lint check with the --fix option. This applies safe corrections automatically using your project-configured linters and formatters.

Does this linting tool support multiple ecosystems like Python and Rust?

Yes, this linting tool supports multiple ecosystems like JavaScript/TypeScript, Python, Rust, and Go. It detects the appropriate tooling to use through your project's configuration files.

What is the best way to enforce consistent code style in a large monorepo?

The best way to enforce consistent code style in a large monorepo is using an automated linting Skill that runs the appropriate tooling to enforce standards and auto-fixes where safe. This reduces manual review time and drift.

Will the linter respect my gitignore and skip ignored directories?

Yes, the linter respects project configuration and ignores ignored directories when running checks. It targets only the relevant working tree or specified path without scanning excluded files.