pr-linter-enforcer_skill

Overview

This skill runs ESLint, Prettier, and stylelint against changed files and reports or applies fixes to keep code consistent and error-free. It detects available linters in the project, limits checks to staged or branch-diff files, and can auto-apply safe fixes on request. Use it to enforce style, catch regressions, and speed up PR reviews.

How this skill works

The skill identifies changed files (staged or branch diff), detects which linters and configs exist, and runs the appropriate tools only on lintable files. It collects and categorizes issues into errors, warnings, and style problems, presents a concise report with suggested fixes, and can run auto-fix commands and re-verify results when asked.

When to use it

• Before opening or merging a PR to ensure code quality and consistency
• When a reviewer flags formatting, style, or lint errors in a diff
• Before committing to enforce project linting policies via pre-commit hooks
• When you need targeted lint checks only on changed files to save time
• When team members disagree on formatting and you want automated enforcement

Best practices

• Run linters only on changed files for fast feedback; run full suites in CI
• Prefer project npm/yarn scripts (npm run lint) if present so behavior matches CI
• Treat errors as must-fix, warnings as review items, and style issues as auto-fixable
• Use lint-staged + husky for pre-commit enforcement to avoid noisy PRs
• Re-run linters after fixes to ensure no new issues were introduced

Example use cases

• A developer asks: 'Can you lint the files in my branch and fix formatting?' — run ESLint/Prettier/stylelint on changed files and apply fixes.
• A reviewer reports multiple style warnings in a PR — generate a categorized lint report highlighting errors vs. style issues.
• Setting up pre-commit checks — suggest lint-staged + husky with commands to auto-fix staged files.
• CI gatekeeping — run detection and full linter commands in CI to block merges on errors.