Verified:GitHub

Quality Tools

Execute standardized linting workflows for multiple languages and tools, including ESLint-based TypeScript checks with configurable severity thresholds and remediation options.

Updated Mar 15, 2025

Search Tags:#code quality #developer tools #code analysis #linting #formatting #type checking

Ready to run

npx skills add https://github.com/yasushiasahi/nix-config --skill quality-tools-yasushiasahi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Quality Tools
Source: https://github.com/yasushiasahi/nix-config/tree/main/home-manager/agent-skills/skills/quality-tools
Command: npx skills add https://github.com/yasushiasahi/nix-config --skill quality-tools-yasushiasahi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill centralizes and standardizes the definitions and usage patterns for various code quality tools, preventing duplication and ensuring consistent application across different agents and projects.

Core Features & Use Cases

Tool Definitions: Provides structured information on linters (ESLint, Go_Tools, Rust_Tools, Nix_Tools, Python_Tools), formatters (Prettier, black, cargo fmt), and type checkers (TypeScript_Compiler, mypy).
Usage Patterns: Defines standard workflows for quality checks, auto-fixing, and incremental checks.
Use Case: An agent needs to ensure code quality before a commit. It can reference this skill to understand the correct commands for ESLint, Prettier, and TypeScript compilation, and follow the quality_check_workflow pattern.

Quick Start

Use the Quality Tools skill to run a full quality check on the project's TypeScript files.

Frequently Asked Questions about Quality Tools

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

FAQPage Schema

How do I standardize code quality checks across multiple programming languages?▼

To standardize code quality checks across multiple programming languages, use centralized tool definitions for linters, formatters, and type checkers. This ensures consistent application of code standards and reproducible codebases across different agents and projects.

What is the best way to run linters and formatters before a code commit?▼

The best way to run linters and formatters before a commit is to follow a standardized quality check workflow. This references correct commands for tools like ESLint and Prettier to execute quality verification and automatic code fixing.

Does this centralized tool knowledge support incremental code checks?▼

Yes, centralized tool knowledge supports incremental code checks. It defines standard workflows for incremental checks alongside quality verification and automatic code fixing, ensuring faster feedback loops during development.

How do I ensure consistent type checking with TypeScript and mypy in my project?▼

To ensure consistent type checking with TypeScript and mypy, reference standardized usage patterns for type checkers. This provides structured information for TypeScript_Compiler and mypy to maintain consistent code standards.

Can I automatically fix formatting issues using Prettier and black?▼

Yes, you can automatically fix formatting issues using Prettier and black. The tool definitions include workflows for automatic code fixing, allowing agents to apply formatters and ensure consistent code standards.