lfe-security-check

Analyze code diffs for OWASP Top-10 vulnerabilities and output Markdown findings.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automatically analyzes code changes for potential security vulnerabilities according to the OWASP Top-10 standard, helping to prevent security breaches before they happen.

Core Features & Use Cases

  • Security Analysis: Conducts a security check based on the OWASP Top-10 standard without the need for external tools.
  • Code Analysis: Analyzes code changes for security vulnerabilities directly within the implementation diff.
  • Output Report: Generates a detailed security findings report in Markdown format.

Quick Start

Run the lfe-inspector command to automatically execute the lfe-security-check sub-skill.

Frequently Asked Questions about lfe-security-check

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

FAQPage Schema
How do I automate OWASP Top-10 security analysis for code changes?

You can automate OWASP Top-10 security analysis for code changes by triggering the `/lfe-inspector` command. This automatically executes the security check to analyze your implementation diff for vulnerabilities and generates a detailed Markdown report.

What is OWASP Top-10 vulnerability detection in code diffs?

OWASP Top-10 vulnerability detection in code diffs is the process of analyzing implementation changes to identify potential security flaws. This approach helps prevent security breaches by evaluating code modifications directly against the OWASP Top-10 standard without external tools.

Do I need external tools to perform LLM reasoning security analysis on my code?

No, you do not need external tools to perform LLM reasoning security analysis on your code. The Skill conducts the security check based on the OWASP Top-10 standard internally and outputs findings directly into a Markdown file.

How does code review for security vulnerabilities generate its findings?

Code review for security vulnerabilities generates its findings by analyzing the implementation diff for threats based on the OWASP Top-10. It outputs the discovered vulnerabilities into a Markdown file and aggregates the results into a final critique report.

What is the best way to check code changes for OWASP vulnerabilities without external dependencies?

The best way to check code changes for OWASP vulnerabilities without external dependencies is using an automated LLM reasoning skill. Triggered by the `/lfe-inspector` command, it analyzes the diff and produces an aggregated Markdown critique report.