skills.rest
takeokunn
takeokunnCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

Quality Tools

Run linting, formatting, and type checks across multi-language codebases.

71|2|Updated Feb 23, 2024
Search Tags:#eslint#prettier#code-quality#static-analysis#lint#type-check
One-click install
npx skills add https://github.com/takeokunn/nixos-configuration --skill quality-tools
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Quality Tools
Source: https://github.com/takeokunn/nixos-configuration/tree/main/home-manager/programs/claude-code/skills/tools/quality-tools
Command: npx skills add https://github.com/takeokunn/nixos-configuration --skill quality-tools

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill centralizes knowledge and usage patterns for code quality tools (ESLint, Prettier, tsc, and related linters) to reduce duplication and accelerate verification across projects.

Core Features & Use Cases

  • Centralized definitions and workflows for common quality checks
  • Reusable patterns for type checking, linting, and formatting
  • Guidance on reporting findings with file:line locations and actionable fixes

Quick Start

Use this Skill to run a standard quality verification workflow across a codebase: perform type checks, lint, and format checks in sequence, and generate a consolidated report of issues.

Frequently Asked Questions about Quality Tools

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

FAQPage Schema
How do I standardize ESLint and Prettier checks across multiple projects?▼

Standardizing ESLint and Prettier checks involves centralizing definitions and reusable patterns for type checking, linting, and formatting to reduce duplication and accelerate code quality verification across projects.

Can I automate code quality verification in CI pipelines and PR checks?▼

Automating code quality verification in CI pipelines and PR checks applies standardized workflows that run type checks, linting, and formatting in sequence to report issues with file:line locations and actionable fixes.

What is the best way to report linting and type checking errors with actionable fixes?▼

Reporting linting and type checking errors with actionable fixes requires generating a consolidated report of issues that pinpoints exact file:line locations to accelerate local development and PR checks.

Does this code quality tooling support multi-language codebases?▼

Supporting multi-language codebases requires automating and standardizing code quality verification using popular tooling like ESLint, Prettier, and tsc across local development workflows and CI pipelines.

How to run a standard quality verification workflow across a codebase?▼

Running a standard quality verification workflow across a codebase requires performing type checks, linting, and formatting in sequence to generate a consolidated report of issues with actionable fixes.

Why use centralized definitions for static analysis and linting?▼

Using centralized definitions for static analysis and linting reduces configuration duplication and accelerates verification by providing reusable patterns for consistent code quality checks across projects.

Related Skills

Explore More Software Engineering Skills→
coreindustriescoreindustries
1

lint

Run linting, formatting, and type checks with auto-fix and strict mode.

Community
Intermediate
Yeachan-HeoYeachan-Heo
38.5k

code-review

Identify and report code quality, security, and maintainability issues in diffs.

Community
Advanced
ysyecustysyecust
40

springboot-verification

Verify Spring Boot projects with builds, static analysis, tests, and security scans.

Community
Advanced
harrytran998harrytran998

Oxlint

Analyze JavaScript and TypeScript code with the Oxlint linter.

Community
Basic