lie-scan

Detect lie-code patterns in codebases using static grep-like scans.

1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/stronghuni/FindLie --skill lie-scan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lie-scan
Source: https://github.com/stronghuni/FindLie/tree/main/lie-scan
Command: npx skills add https://github.com/stronghuni/FindLie --skill lie-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly detects lie-code indicators in a codebase without executing code, helping teams catch incorrect or deceptive patterns early in development.

Core Features & Use Cases

  • Pattern-based checks for common lie-code indicators like mock data, stubs, empty catches, placeholder URLs, dead code, and duplicated files.
  • CI-friendly mode with machine-readable exit codes for seamless integration into pipelines.
  • Use Case: run this scan before commits or in CI to surface suspected issues and prioritize fixes.

Quick Start

Run the lie-scan skill to perform a fast static scan for lie patterns and report findings in under 30 seconds.

Frequently Asked Questions about lie-scan

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

FAQPage Schema
How do I detect lie-code patterns like mock data and empty catches in a JavaScript codebase?

Run static pattern-based scanning to detect lie-code patterns like mock data and empty catches in a JavaScript codebase without executing code. This fast grep-like scan surfaces deceptive patterns early for prioritized fixes.

Can I integrate static lie-code scanning into my CI-CD pipeline?

Yes, static lie-code scanning integrates into CI-CD pipelines using CI-friendly mode with machine-readable exit codes and structured findings. This enables seamless pipeline automation and early issue detection.

What is lie-code and how does static pattern detection identify it?

Lie-code refers to incorrect or deceptive programming patterns like stubs, dead code, and duplicated files. Static pattern detection identifies it by scanning codebases with grep-like rules to surface these indicators quickly without executing code.

Does this static pattern scanner work with Python and TypeScript files?

Yes, this static pattern scanner works with Python and TypeScript files, along with JavaScript and other common stacks. It performs fast grep-like scans across multiple languages to detect deceptive patterns consistently.

What's the best way to run a pre-commit check for placeholder URLs and dead code?

The best way to run a pre-commit check for placeholder URLs and dead code is using a fast static pattern scanner that delivers structured findings in under 30 seconds. This catches and surfaces deceptive patterns before committing changes.

Why does static scanning report false positives for duplicated files?

Static scanning may report false positives for duplicated files because it uses grep-like pattern matching without executing code or analyzing runtime context. It flags suspected lie-code indicators early, requiring developers to review structured findings manually.