lint

Run TypeScript type checks, ESLint linting, and Prettier formatting across the Terrae codebase.

243|5|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/alamenai/terrae --skill lint-alamenai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint
Source: https://github.com/alamenai/terrae/tree/main/.claude/skills/lint
Command: npx skills add https://github.com/alamenai/terrae --skill lint-alamenai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual code hygiene tasks across the Terrae codebase slow development and introduce bugs. This skill automates linting, type checks, and formatting to enforce consistency and catch issues early.

Core Features & Use Cases

  • Run Type Checking: Executes TypeScript checks without emitting files to verify types across the repository.
  • Run Linting: Runs ESLint to identify style issues, potential bugs, and enforce coding standards.
  • Format Validation: Checks code formatting with Prettier to ensure a uniform style across projects.
  • Use Case: Before submitting a PR, run the suite to surface type or lint errors and formatting issues.

Quick Start

Run lint, type-check, and format checks across the Terrae repository.

Frequently Asked Questions about lint

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

FAQPage Schema
How do I automate ESLint, Prettier, and TypeScript type checking before a PR?

Automate linting, type checking, and formatting by running ESLint, Prettier, and npx tsc across your codebase. This surfaces type errors, lint violations, and formatting issues early, offering auto-fix and re-verification until all checks pass.

What is the best way to fix TypeScript and lint errors iteratively?

The best way to fix TypeScript and lint errors iteratively is to run automated checks that identify violations and offer auto-fix for linting and auto-formatting, followed by re-verification until all type and style checks pass.

Can I run TypeScript type checks without emitting JavaScript files?

Yes, you can run TypeScript type checks without emitting files by executing npx tsc. This verifies types across your repository to catch type errors early without generating compiled output.

Does this linting and formatting automation work with TypeScript projects?

Yes, this automation targets TypeScript projects specifically, using npx tsc for type verification, ESLint for coding standards, and Prettier to enforce uniform formatting style across the codebase.

Why does code formatting and linting fail before submitting a pull request?

Code formatting and linting fails before a PR due to style violations, potential bugs, or type errors. Running ESLint, Prettier, and TypeScript checks identifies these issues early so you can apply auto-fixes and re-verify.

What are the limitations of automated code formatting and lint checks?

Automated lint and formatting checks are limited to surfacing type errors, lint violations, and formatting issues. They require iterative manual or auto-fix application and re-verification until all checks pass, rather than fixing logic bugs.