Agent skill
plan-lower-code-complexity
This skill should be used when reducing the cognitive complexity threshold of the codebase. It lowers the threshold by 2, identifies functions that exceed the new limit, generates a brief with refactoring strategies, and creates a plan with tasks to fix all violations.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/plan-lower-code-complexity-codyswanngt-lisa
SKILL.md
Lower Code Complexity
Reduces the cognitive complexity threshold by 2 and fixes all violations.
Step 1: Gather Requirements
- Read current threshold from eslint config (cognitive-complexity rule)
- Calculate new threshold: current - 2 (e.g., 15 -> 13)
- Run lint with the new threshold to find violations:
bash
bun run lint 2>&1 | grep "cognitive-complexity" - Note for each violation:
- File path and line number
- Function name
- Current complexity score
If no violations at new threshold, report success and exit.
Step 2: Compile Brief and Delegate
Compile the gathered information into a structured brief:
Reduce cognitive complexity threshold from [current] to [new].
Functions exceeding threshold (ordered by complexity):
1. [file:function] (complexity: X, target: [new]) - Line Y
2. ...
Configuration change: [eslint config path], cognitive-complexity from [current] to [new]
Refactoring strategies: extract functions, early returns, extract conditions, use lookup tables
Verification: `bun run lint 2>&1 | grep "cognitive-complexity" | wc -l` → Expected: 0
Invoke /plan-execute with this brief to create the implementation plan.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?