skills.rest
Avihusitton
AvihusittonCOMMUNITY
Explore all skills by this author →
GitHub

logic-lens

Detect logic flaws, race conditions, and security risks in code reviews.

1|Updated May 10, 2026
Search Tags:#static analysis#code review#claude code#security scan#bug detection#logic analysis
One-click install
npx skills add https://github.com/Avihusitton/gil-therapy --skill logic-lens
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: logic-lens
Source: https://github.com/Avihusitton/gil-therapy/tree/main/.agents/skills/logic-lens
Command: npx skills add https://github.com/Avihusitton/gil-therapy --skill logic-lens

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Traditional code linters and static analysis tools only catch syntax errors and style violations, missing critical logical flaws, race conditions, and security vulnerabilities that only emerge when reasoning through code execution paths.

Core Features & Use Cases

  • 9-Category Logic Analysis: Scans code for null/undefined handling gaps, type safety issues, concurrency race conditions, unmanaged resources, injection vulnerabilities, boundary condition errors, algorithm flaws, state inconsistencies, and API contract violations.
  • Security-Sensitive Code Audits: Review authentication, payment, and file access code paths to catch security anti-patterns before deployment.
  • Debugging Complex Issues: Identify hard-to-find bugs in business logic where standard linters return no errors.
  • Legacy Code Onboarding: Map risk areas in unfamiliar codebases to prioritize review and refactoring efforts.

Quick Start

Use the logic-lens skill to review all files changed in your current Git branch for security and logic issues before you open a pull request.

Frequently Asked Questions about logic-lens

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

FAQPage Schema
How do I catch logic bugs and security risks that static analysis tools miss?▼

To catch logic bugs and security risks that static analysis misses, you can perform deep logic-driven code review to analyze execution paths for concurrency race conditions and injection vulnerabilities.

What is logic-driven code review and when do I need it for legacy refactoring?▼

Logic-driven code review applies formal reasoning across 9 risk categories to detect state inconsistencies and API contract violations, making it essential for mapping risk areas before legacy code refactoring.

How do I review changed Git files for security vulnerabilities before a pull request?▼

To review changed Git files for security vulnerabilities before a pull request, run a logic analysis scan to check authentication, payment, and file access code paths for anti-patterns.

Does this deep code review detect null handling gaps and concurrency race conditions?▼

Yes, deep code review detects null handling gaps and concurrency race conditions by applying formal reasoning frameworks across 9 risk categories including type safety and unmanaged resources.

What's the best way to audit authentication code paths for security anti-patterns?▼

The best way to audit authentication code paths for security anti-patterns is to perform security-sensitive code audits that apply formal reasoning to detect injection vulnerabilities and API contract violations.

Related Skills

Explore More Software Engineering Skills→
SOLEROMSOLEROM

security-review

Identify security vulnerabilities in codebases and configurations with a repeatable review process.

Community
Advanced
cc01cccc01cc
4

multi-package-coverage-audit

Consolidate test coverage gaps across multi-package monorepos into prioritized test plans.

Community
Intermediate
nguyenphpnguyenphp
41

lint-and-validate

Run linters, type checkers, and security audits across Node.js and Python projects.

Community
Intermediate
zajcazajca
2

go-linting

Configure golangci-lint with recommended Go linters for static analysis.

Community
Basic