Logic Locate — Testing skill for Claude Code
Locate the root cause of a confirmed failure — use when you have a stack trace, failing test, or wrong output.
How to install Logic Locate
Installs to ~/.claude/skills/hyhmrright-logic-lens-logic-locate/SKILL.md
mkdir -p ~/.claude/skills/hyhmrright-logic-lens-logic-locate && curl -fsSL https://raw.githubusercontent.com/hyhmrright/logic-lens/HEAD/commands/logic-locate.md -o ~/.claude/skills/hyhmrright-logic-lens-logic-locate/SKILL.md Restart Claude Code, or start a new session, for it to be picked up.
What Logic Locate does
description: Locate the root cause of a confirmed failure — use when you have a stack trace, failing test, or wrong output allowed-tools: Skill
Use the Skill tool to invoke `logic-lens:logic-locate`, then follow its instructions exactly. $ARGUMENTS
Alternatives in Testing
- Webapp Testing — Test local web applications using Playwright for UI verification and debugging 94.1k ★
- #29 — #52, #103) 92.5k ★
- /test Routing — Vérifie le routing de commandes RTK sans exécution (dry-run) 25.5k ★
Full documentation available on GitHub
View Source RepositoryRelated Skills
Logic Review
Review code for logic bugs — use when you suspect something is wrong but have no failing test yet
Cfn Pseudo
SPARC Pseudocode phase. Trace logic, enumerate branches, find failure paths, verify branch coverage BEFORE wri
Systematic Debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase frame
Analyze Test Report
Phân tích test report — automation (Playwright/Allure/JUnit/TestNG) hoặc manual (execution_report.md / retest_
Canary Failure Impact
Trace the downstream impact of a test, function, or code path failing undetected — produces a severity label a
Debugging
Debug a bug, crash, failing test, or broken build to root cause
Related Agents
Codex Debugger
Root-cause a failing test, crash, stack trace, or misbehaving feature by delegating the investigation to OpenA
Ndv Diagnose
Debugging specialist. Use when you have a bug, failing test, stack trace, unexpected behavior, or anything bro
Tp Debugger
PROACTIVELY use this when the user reports a bug, stack trace, error message, failing behaviour, or asks "why