enforcing-code-linting

Lint and fix changed files in JavaScript/TypeScript pull requests with ESLint, Prettier, and stylelint.

6|2|Updated Jan 18, 2026

Search Tags:#eslint #prettier #code-quality #lint #pull-request #stylelint

Ready to run

npx skills add https://github.com/WesleySmits/agent-skills --skill enforcing-code-linting

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: enforcing-code-linting
Source: https://github.com/WesleySmits/agent-skills/tree/main/.agent/skills/pr-linter-enforcer
Command: npx skills add https://github.com/WesleySmits/agent-skills --skill enforcing-code-linting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Runs ESLint, Prettier, and stylelint against changed files and suggests or applies fixes. Use when the user mentions linting, code style, PR review, formatting issues, or wants to check code quality before committing.

Core Features & Use Cases

Changed-file linting: Runs ESLint, Prettier, and stylelint on only modified files in the working tree or PR branch.
Quality enforcement: Detects style, syntax, and formatting issues and suggests or applies fixes automatically.
Use Case: While reviewing a PR, automatically fix common lint errors and ensure consistent formatting before merging.

Quick Start

Ask the AI to identify changed files, run the appropriate linters, and apply requested fixes before you commit.

Frequently Asked Questions about enforcing-code-linting

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

FAQPage Schema

How do I automatically lint and fix code changes in a pull request?▼

You can automatically lint and fix code changes in a pull request by running ESLint, Prettier, and stylelint on modified files to detect formatting issues and apply fixes before committing.

Can I run ESLint and Prettier only on changed files during a PR review?▼

Yes, you can run ESLint and Prettier only on changed files during a PR review by identifying modified files in the working tree and targeting linters specifically at that subset.

What is the best way to enforce code quality and consistent formatting before merging?▼

The best way to enforce code quality and consistent formatting before merging is to run linters like ESLint, Prettier, and stylelint on changed files and auto-apply fixes to resolve syntax and style issues.

Does this code linting process work with JavaScript and TypeScript projects?▼

Yes, this code linting process works with JavaScript and TypeScript projects by detecting configured linters such as ESLint, Prettier, and stylelint to identify and fix code style issues.

Why should I lint only modified files instead of the entire codebase?▼

Linting only modified files instead of the entire codebase targets changed files in your PR branch, reducing processing time while still catching style, syntax, and formatting issues before you commit.

How do I run stylelint on changed files to check CSS code quality?▼

To run stylelint on changed files to check CSS code quality, identify modified files in your working tree, execute the linter on that targeted set, and apply suggested fixes to ensure consistent styling.