logic-audit

Detect contradictions, unsupported inferences, and missing cases in bounded source sets.

Updated Jul 20, 2026
One-click install
npx skills add https://github.com/srinitude/skills --skill logic-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: logic-audit
Source: https://github.com/srinitude/skills/tree/main/skills/logic-audit
Command: npx skills add https://github.com/srinitude/skills --skill logic-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps you detect contradictions, missing links, unsupported inferences, and authority conflicts in a bounded set of sources before you make a decision or publish a conclusion.

Core Features & Use Cases

  • Logical consistency checks: Compare claims, requirements, evidence, and conclusions for direct conflicts, scope drift, quantifier changes, and conditional reversals.
  • Gap and proof analysis: Identify missing cases, incomplete premises, weak evidence chains, and component-only evidence being overstated as whole-proof.
  • Repair-oriented auditing: Produce the smallest coherent fix while preserving intent, authority, and exact methods.
  • Use case: Audit a policy, plan, or specification set and return a bounded finding ledger that distinguishes confirmed issues from unresolved uncertainty.

Quick Start

Ask the skill to audit a bounded source set for contradictions, missing cases, and proof gaps, then report the findings with the smallest safe repair.

Frequently Asked Questions about logic-audit

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

FAQPage Schema
How do I find contradictions and logical gaps in a set of policy or specification documents?

To detect contradictions in policies or specifications, normalize the bounded source set, trace dependencies, and test for counterexamples. This process identifies direct conflicts, scope drift, and unsupported inferences before you finalize decisions.

What is logical consistency checking and when do I need it for research notes?

Logical consistency checking compares claims, evidence, and conclusions to identify missing cases and weak evidence chains. You need it for research notes when scope, time, modality, or quantifiers may drift across mixed evidence sources.

How do I audit a bounded source set for authority conflicts and missing cases?

Audit a bounded source set by applying source normalization and counterexample testing to detect authority conflicts and missing cases. The process returns a bounded finding ledger that distinguishes confirmed issues from unresolved uncertainty.

What is the best way to repair logical contradictions without changing the original intent?

The best way to repair logical contradictions is through bounded repair, which produces the smallest coherent fix while preserving intent, authority, and exact methods. It operates within explicit evidence limits to maintain source validity.

Can I use logic auditing to check specifications for quantifier changes and conditional reversals?

Yes, you can audit specifications to check for quantifier changes and conditional reversals. The auditing process compares requirements and claims to detect scope drift and logical conflicts across the bounded source set.

What are the limitations of using automated logical inference for evidence chain analysis?

A key limitation is that logical inference analysis requires a strictly bounded source set and cannot resolve issues beyond explicit evidence limits. It distinguishes confirmed findings from unresolved uncertainty but cannot repair gaps outside the source boundaries.