Verified:GitHub

logic-auditor

Scans source files for logic, architecture, and consistency errors before deployment.

1|Updated Apr 23, 2026

Search Tags:#code review #quality gate #code audit #consistency check #pre-push #z-index #symlink validation

One-click install

npx skills add https://github.com/tkogut/agents-os-core --skill logic-auditor-tkogut

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: logic-auditor
Source: https://github.com/tkogut/agents-os-core/tree/main/global_skills/logic-auditor
Command: npx skills add https://github.com/tkogut/agents-os-core --skill logic-auditor-tkogut

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often ship with hidden inconsistencies such as z-index conflicts, broken symlinks, or inconsistent naming that only surface after deployment. This Skill performs a pre-deployment audit handshake that verifies logical, architectural, and mathematical consistency before code is pushed. ## Core Features & Use Cases - Source File Scanning: Detects common defects including z-index conflicts, broken symlinks, and inconsistent naming conventions. - Structured Review Report: Returns findings in a concise caveman-review format for fast triage. - Audit Handshake Gate: Confirms Plan-Alignment and Math-Consistency before every git push or after completing Track Alpha/Beta work. - Use Case: Before pushing a UI change, run the audit to catch a z-index conflict between overlapping modal layers and a broken symlink introduced during refactoring. ## Quick Start Ask the AI to run a logic audit on the current project files and report any consistency issues before pushing to git.

Frequently Asked Questions about logic-auditor

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

FAQPage Schema

How do I check code consistency before git push?▼

Run the logic audit before every git push to scan source files for z-index conflicts, broken symlinks, and inconsistent naming. It returns a caveman-review report confirming plan alignment and math consistency.

What errors does a pre-deployment code audit detect?▼

This audit detects z-index conflicts in UI layers, broken symlinks in the project structure, and inconsistent naming across source files. Findings are returned in a compact caveman-review format.

When should the logic audit be triggered in a workflow?▼

Trigger it before every git push or after completing Track Alpha/Beta work in the AGENTS-OS swarm workflow. It acts as an audit handshake gate verifying the change set.

Does the logic auditor fix the issues it finds?▼

No, it only scans and reports issues in a caveman-review format. Fixing the detected z-index conflicts, broken symlinks, or naming inconsistencies is left to the developer or a separate remediation step.