lint-format

Enforce linting and formatting checks on TypeScript projects before commits.

1|Updated May 26, 2026
One-click install
npx skills add https://github.com/virajp/ai-plugins --skill lint-format-virajp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint-format
Source: https://github.com/virajp/ai-plugins/tree/main/plugins/typescript/skills/lint-format
Command: npx skills add https://github.com/virajp/ai-plugins --skill lint-format-virajp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents inconsistent code quality and formatting issues by enforcing a reliable lint and format gate before commits.

Core Features & Use Cases

  • Lint Validation: Runs @askviraj/linter to detect correctness issues across supported languages and file types.
  • Formatting Enforcement: Uses dprint and package sorting rules to maintain consistent code layout and structure.
  • Use Case: Ensure a TypeScript project passes automated quality checks before changes are committed or merged.

Quick Start

Ask the lint-format skill to check and fix formatting and lint issues in the current repository.

Frequently Asked Questions about lint-format

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

FAQPage Schema
How do I enforce ESLint and formatting checks before commits in a TypeScript project?

You can prevent code quality regressions before commits by running automated lint validation and dprint formatting checks. This applies safe fixes to source files and ensures TypeScript projects maintain consistent coding standards before changes are merged.

What is the best way to automate code quality gates for TypeScript repositories?

Automated code quality gates use configured lint and formatter tooling to validate source files. By running @askviraj/linter and dprint, the gate detects correctness issues and applies package sorting rules to maintain consistent code layout.

Can I automatically fix lint and formatting issues in my repository?

Yes, automated lint and format checks can apply safe fixes to your source files. You can ask the system to check and fix formatting and lint issues in the current repository to keep code clean and commits ready.

Do I need to configure dprint and ESLint separately before running quality checks?

Configured lint and formatter tooling is required to validate source files and apply safe fixes. The quality gate relies on existing dprint formatting and ESLint configuration to detect correctness issues and enforce consistent layout standards.

Why should I use dprint for formatting instead of other category-level tools?

Dprint maintains consistent code layout and structure while applying package sorting rules. It works alongside ESLint configuration to provide a reliable formatting and lint gate that prevents inconsistent code quality before commits.