Agent skill · software engineering · sickn33
logic-locate
Locate the root cause of a CONFIRMED failure via backward-then-forward semi-formal tracing.
Why this skill is useful
Adds a structured approach to debugging with specific tracing methods and reporting formats that the AI wouldn't reliably generate on its own.
What it needs
About 2k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Logic-Lens — Fault Locate When to Use Use this skill when you need locate the root cause of a CONFIRMED failure via backward-then-forward semi-formal tracing. Trigger when the user provides a stack trace, failing assertion, error message, or specific wrong-value observation — "find the bug", "this test is failing", "track down this crash", "why is... Setup Use lazy loading per ../shared/common.md §13: 1. Read ../shared/common.md only for language, Iron Law, Fault Confidence, scope routing, Remedy discipline, config fields, and loading budget. 2. Read only the relevant step in logic-locate-guide.md as you reach it. 3. Load ../shared/logic-risks.md, ../shared/semiformal-guide.md, ../shared/semiformal-checklist.md, and ../shared/report-template.md on demand when the current step needs them. Process Step 0. Language + scope routing. Detect language per common.md §1. Confirm a concrete failure exists (stack trace, failing assertion, specific wrong value). If only a suspicion, switch to logic-review. Step 1. Understand the failure (guide Step 1) — observed behavior, expected behavior, reproduction path. Step 2. Identify the entry point (guide Step 2) — failing test, outermost application frame, or request handler — whichever is closest to the failure. Stay inside the failure cone first: stack frames, failing test fixture, directly called local functions, and config/env values read on that path. Do not scan unrelated modules unless the trace crosses into them. Step 3. Trace backward from the failure point (guide Step 3) — walk each value and state back to its origin, building premises at every hop. Step 4. Trace forward to confirm (guide Step 4) — from the suspected root, verify the trace reaches the observed symptom. Step 5. Interprocedural tracing if a callee is implicated (guide Step 5) — trace into the callee; check return values under observed conditions, unhandled exceptions, shared-state mutation. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/logic-locate--06e87a