lfe-perf-check

Detect performance anti-patterns in code diffs and write findings to Markdown.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automatically inspects code changes for common performance issues, helping maintain optimal performance without manual analysis.

Core Features & Use Cases

  • Performance Analysis: Identifies resource leaks, N+1 queries, unbounded growth, and algorithmic complexity in code changes.
  • Output Generation: Writes detailed performance findings in a structured Markdown file.
  • Integration: Called by the lfe-inspector Skill during the inspection phase of the LFE process.

Quick Start

To perform a performance check on the current code changes, execute /lfe-inspector.

Frequently Asked Questions about lfe-perf-check

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

FAQPage Schema
How do I automate performance inspection for code changes?▼

You can automate performance inspection by running the `lfe-inspector` command, which triggers this Skill to analyze code diffs and detect common performance anti-patterns automatically.

What performance anti-patterns can be detected through diff analysis?▼

Diff analysis identifies resource leaks, N+1 queries, unbounded growth, and algorithmic complexity issues within your code changes.

How does LLM reasoning work for code analysis during performance checks?▼

LLM reasoning analyzes your code diffs to evaluate performance impacts, identifying structural anti-patterns and generating detailed findings in a structured Markdown file.

Do I need to install dependencies to use this performance inspection tool?▼

No additional dependencies are required to use this performance inspection tool, as it operates independently with its own scripts to analyze code changes.

Can I use this code analysis tool outside of the Library-First Engineering process?▼

While designed for the Library-First Engineering inspection phase, the tool can independently analyze code diffs for performance issues and output structured Markdown findings.