lfe-dep-audit

Review dependency manifests for risky version patterns and major changes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the review of dependency manifest files, flagging risky version patterns and major changes, and prompts for human-run audits, ensuring security and build integrity.

Core Features & Use Cases

  • Dependency Manifest Review: Automatically scans and reviews dependency manifest files for versioning issues and security risks.
  • Human-Run Audit: Generates a structured instruction for manual review by a human, maintaining tool agnosticism and avoiding false positives.
  • Integration with Inspector: Designed to be used as a sub-skill by the Inspector in the LFE framework.

Quick Start

To run the dependency audit, execute /lfe-inspector and ensure lfe-dep-audit: true is set in .docs/quality/inspector-config.md.

Frequently Asked Questions about lfe-dep-audit

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

FAQPage Schema
How do I automate a dependency manifest audit for risky version patterns?

A dependency manifest audit scans your manifest files to flag risky version patterns and major changes, generating structured instructions for human review to ensure security and build integrity. It automates detection while requiring manual confirmation.

How do I run a dependency manifest review within the LFE framework?

To run a dependency manifest review in the LFE framework, execute the /lfe-inspector command and ensure lfe-dep-audit: true is set in the .docs/quality/inspector-config.md file to trigger the automated scan.

Does the LFE Inspector sub-skill automatically update dependency versions?

No, the LFE Inspector sub-skill does not update versions. It generates a structured instruction for a human-run audit to review flagged versioning issues, maintaining tool agnosticism and avoiding false positives.

What is the best way to review dependency manifests for major changes without false positives?

The best way to review dependency manifests for major changes without false positives is using an automated audit that generates structured instructions for human review, ensuring tool agnosticism and manual confirmation of security risks.

Why does dependency audit require human review after scanning manifests?

Dependency audit requires human review because the automated scan generates structured instructions for manual verification to avoid false positives. This maintains build integrity by ensuring a human confirms risky version patterns before changes are applied.