lfe-inspector

Validate LFE-compliant project code against domain truth and baselines.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill validates the implementation of an LFE-compliant project against domain truth, validation baselines, and numerical baselines, ensuring code accuracy and preventing regressions.

Core Features & Use Cases

  • Implementation Verification: Verify that the codebase matches documented domain knowledge and validation baselines.
  • Debugging: Identify and diagnose regressions or math drift.
  • Automated Checks: Execute a series of automated checks to ensure code integrity.
  • Use Case: Integrate this Skill into the LFE development workflow to validate features before they are sent to the Archivist.

Quick Start

Execute the /lfe-inspector command within your LFE project to verify the current implementation.

Frequently Asked Questions about lfe-inspector

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

FAQPage Schema
How do I validate code implementation against domain truth in an LFE-compliant project?

You can validate code implementation by checking the codebase against domain truth, validation baselines, and numerical baselines to ensure accuracy and prevent regressions. This Skill handles verification for unfamiliar code areas and provides manual verification options.

Why does my LFE project have math drift or regressions after recent changes?

Math drift and regressions occur when code implementation deviates from documented domain knowledge or numerical baselines. Running automated checks against validation baselines identifies and diagnoses these specific regressions before features are sent to the Archivist.

What is the best way to prevent regressions in LFE-compliant projects before sending features to the Archivist?

The best way to prevent regressions is integrating automated validation checks into your LFE development workflow. Execute the validation command within your project to verify the current implementation against domain truth and numerical baselines before submission.

Can I run security and performance checks alongside code validation in LFE projects?

Yes, code validation incorporates sub-skills for security, performance, and complexity checks. These automated checks run together to ensure overall code integrity and accuracy within LFE-compliant projects during the verification process.

How do I verify code accuracy in unfamiliar code areas of an LFE project?

To verify code accuracy in unfamiliar areas, the Skill provides manual verification capabilities and checks the implementation against documented domain knowledge. This ensures the unfamiliar code matches validation baselines and maintains required integrity.

Does LFE code validation require any specific dependencies or environment setup?

No specific dependencies are required to use this validation functionality. The Skill operates using included scripts and references to perform automated checks against domain truth and numerical baselines within your existing LFE-compliant project environment.