plan-reduce-max-lines_skill

Overview

This skill reduces the maximum allowed lines per file and produces a concrete plan to fix any violations. It updates the ESLint threshold, finds files that exceed the new limit, and generates a brief and task list to split oversized files and verify compliance.

How this skill works

The skill reads the current ESLint thresholds configuration and applies the requested max-lines value. It runs the linter to detect files violating the new limit, collects file paths and current line counts, and compiles a short brief listing offending files and suggested refactor strategies. Finally, it produces a step-by-step plan with split/refactor tasks and verification commands.

When to use it

• You want to enforce a lower max-lines limit across the TypeScript codebase.
• Before merging a policy change that tightens file size standards.
• When preparing for a large reorganization or modularization effort.
• If automated checks report growing file sizes and you need a remediation plan.

Best practices

• Confirm the desired numeric threshold before running the change to avoid unnecessary churn.
• Run lint locally or in CI with the new threshold to reproduce violations reliably.
• Order files by descending line count so highest-impact splits are prioritized.
• Prefer extracting cohesive modules, not arbitrary line cuts—preserve behavior and tests.
• Add targeted unit tests or integration checks when extracting logic to prevent regressions.

Example use cases

• Lower max-lines from 1000 to 500 to improve code readability and reviewability.
• Enforce a stricter limit as part of a campaign to modularize legacy services.
• Create a task plan for an engineering team to split the top 20 largest files.
• Automate verification in CI by changing eslint.thresholds.json and failing builds until violations are fixed.