static-code-analysis-typescript

Configure ESLint, Prettier, and GitHub Actions for TypeScript static analysis.

1|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/gniazdowski-luk/rolnopol-atf --skill static-code-analysis-typescript
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: static-code-analysis-typescript
Source: https://github.com/gniazdowski-luk/rolnopol-atf/tree/main/.github/skills/static-code-analysis-typescript
Command: npx skills add https://github.com/gniazdowski-luk/rolnopol-atf --skill static-code-analysis-typescript

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create, review, or modernize static code analysis for Node.js and TypeScript repositories. Use for ESLint flat config, typescript-eslint, TypeScript/tsconfig, Prettier split, import sorting, Husky, lint-staged, package.json scripts, engines, naming conventions, CI quality gates, and GitHub Actions workflows.

Core Features & Use Cases

  • Establish or upgrade static analysis configurations to ensure consistent code quality across TypeScript projects.
  • Align linting, formatting, type checking, and CI quality gates with modern tooling (ESLint, Prettier, typescript-eslint, tsconfig, and GitHub Actions).
  • Tighten repository hygiene through Husky and lint-staged hooks, with clear script naming and engine constraints for CI.

Quick Start

Configure a TypeScript project to enable robust static analysis and testing workflows.

Frequently Asked Questions about static-code-analysis-typescript

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

FAQPage Schema
How do I set up ESLint flat config and Prettier for a TypeScript project?

Configure ESLint flat config alongside Prettier split and tsconfig.json to enforce linting, formatting, and type checking for Node.js and TypeScript projects.

What's the best way to add Husky and lint-staged hooks to a Node.js repository?

Add Husky and lint-staged hooks with package.json scripts to tighten repository hygiene by running static analysis automatically before commits.

How do you configure CI quality gates using GitHub Actions workflows for TypeScript?

Configure CI quality gates via GitHub Actions workflows that execute static analysis, type checking, and linting scripts defined in package.json.

Can I use this to modernize static code analysis configurations with typescript-eslint?

Yes, you can modernize static code analysis by upgrading to typescript-eslint, aligning import sorting, and applying clear engine constraints for CI reproducibility.

Why do I need explicit tooling configuration like eslint.config.mjs for static analysis?

Explicit tooling configuration via eslint.config.mjs, tsconfig.json, and package.json scripts is required to ensure reproducible static analysis and formatting environments across CI workflows.

Does this static analysis setup support import sorting and naming conventions?

Yes, the static analysis setup governs import sorting and naming conventions alongside linting and formatting to establish consistent code quality across TypeScript projects.