lfe-complexity-check

Analyze modified files for code complexity indicators using pure LLM reasoning.

43|2|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/StChiotis/Library-First-Engineering --skill lfe-complexity-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lfe-complexity-check
Source: https://github.com/StChiotis/Library-First-Engineering/tree/main/.agents/skills/lfe-complexity-check
Command: npx skills add https://github.com/StChiotis/Library-First-Engineering --skill lfe-complexity-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The LFE Complexity Check Skill unit addresses the issue of complex, hard-to-maintain code. It helps identify potential problems with code structure that could lead to confusion or difficulty in future modifications.

Core Features & Use Cases

  • Complexity Analysis: Analyzes code for indicators such as cyclomatic complexity, excessive nesting, oversized functions, and cognitive load.
  • Inspector Sub-Skill: Used as part of the LFE Inspector's workflow to provide a critique of the codebase.
  • Triggered by LFE Inspector: The Skill is invoked by the /lfe-inspector command when configured to do so.

Quick Start

To start the complexity check, run the /lfe-inspector command after performing a build step in your project.

Frequently Asked Questions about lfe-complexity-check

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

FAQPage Schema
How do I check code complexity for maintainability without external tools?

Code complexity and maintainability analysis is performed using pure LLM reasoning without external tooling. The skill evaluates modified files within the LFE Inspector framework to identify indicators like cyclomatic complexity, excessive nesting, and oversized functions.

What code complexity metrics are detected during an analysis?

Code complexity metrics detected include cyclomatic complexity, excessive nesting, oversized functions, and cognitive load. The analysis targets these structural indicators within modified files to highlight potential maintainability issues before they cause confusion.

How do I run a complexity analysis on modified files?

To run a complexity analysis on modified files, execute the `/lfe-inspector` command after completing a build step in your project. The LFE Inspector framework triggers the complexity check as part of its configured workflow.

Does the LFE complexity check require external dependencies or linters?

The LFE complexity check does not require external dependencies or linters. It utilizes pure LLM reasoning to evaluate diff scopes and generate maintainability findings entirely within the LFE Inspector's framework.

Why analyze code complexity only on modified files instead of the whole codebase?

Analyzing code complexity on modified files focuses maintainability checks on recent changes. The skill operates on diff scopes to target structural issues introduced by recent modifications rather than evaluating the entire codebase.