Skill

plan-reduce-max-lines-per-function

This skill should be used when reducing the maximum lines per function threshold and fixing all violations. It updates the eslint threshold configuration, identifies functions exceeding the new limit, generates a brief with refactoring strategies, and creates a plan with tasks to split oversized functions.

Install

npx claudepluginhub codyswanngt/lisa --plugin lisa

Tool Access

This skill is limited to using the following tools:

ReadBashGlobGrep

Preview

Target threshold: $ARGUMENTS lines per function

SKILL.md

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

139.2k

mcp-builder

9 files

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

anthropics-skills-13

124.2k

canvas-design

20 files

Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.

anthropics-skills-13

124.2k

Stats

Parent Repo Stars1

Parent Repo Forks2

Last CommitMar 5, 2026

Actions

View Source View Plugin View on GitHub View README

plan-reduce-max-lines-per-function

Reduce Max Lines Per Function

Target threshold: $ARGUMENTS lines per function

If no argument provided, prompt the user for a target.

Step 1: Gather Requirements

Read current config from eslint thresholds (eslint.thresholds.json or similar)

Run lint with the new threshold to find violations:

bun run lint 2>&1 | grep "max-lines-per-function"

Note for each violation:

File path and line number
Function name
Current line count

If no violations at $ARGUMENTS, report success and exit.

Step 2: Compile Brief and Delegate

Compile the gathered information into a structured brief:

Reduce max lines per function threshold to $ARGUMENTS. Functions exceeding threshold (ordered by line count): 1. [file:function] (lines: X, target: $ARGUMENTS) - Line Y 2. ... Configuration change: eslint.thresholds.json, maxLinesPerFunction to $ARGUMENTS Refactoring strategies: extract functions, early returns, extract conditions, use lookup tables, consolidate logic Verification: `bun run lint 2>&1 | grep "max-lines-per-function" | wc -l` → Expected: 0

Invoke /plan-execute with this brief to create the implementation plan.

Reduce Max Lines Per Function

Target threshold: $ARGUMENTS lines per function

If no argument provided, prompt the user for a target.

Step 1: Gather Requirements

Read current config from eslint thresholds (eslint.thresholds.json or similar)

Run lint with the new threshold to find violations:

bun run lint 2>&1 | grep "max-lines-per-function"

Note for each violation:
- File path and line number
- Function name
- Current line count

If no violations at $ARGUMENTS, report success and exit.

Step 2: Compile Brief and Delegate

Compile the gathered information into a structured brief:

Reduce max lines per function threshold to $ARGUMENTS.

Functions exceeding threshold (ordered by line count):
1. [file:function] (lines: X, target: $ARGUMENTS) - Line Y
2. ...

Configuration change: eslint.thresholds.json, maxLinesPerFunction to $ARGUMENTS

Refactoring strategies: extract functions, early returns, extract conditions, use lookup tables, consolidate logic

Verification: `bun run lint 2>&1 | grep "max-lines-per-function" | wc -l` → Expected: 0

Invoke /plan-execute with this brief to create the implementation plan.