Trace runtime exceptions and failing tests to their root-cause code lines.
npx skills add https://github.com/CuongTran69/tramthientra --skill fix-cuongtran69
Please help me install this Agent Skill. Skill: fix Source: https://github.com/CuongTran69/tramthientra/tree/main/.augment/skills/fix Command: npx skills add https://github.com/CuongTran69/tramthientra --skill fix-cuongtran69
This Skill helps engineers locate and fix bugs by guiding the investigation from observable symptom to the exact line of code that causes the failure, reducing time spent on guesswork and preventing superficial fixes.
Use the fix skill to investigate a failing test by invoking explore first, run a semantic search for the error or affected function, grep for suspect assignments or error strings, read the candidate files to find the exact offending line, and propose a targeted fix with test suggestions.
High-intent search queries and answers about installing and using this skill.
To trace a runtime exception to its root-cause line, apply structured debugging methods like backward reasoning and semantic codebase retrieval to locate suspect assignments, then use grep for exact pattern matching and read files for line-by-line inspection.
The best way to triage a regression is to use delta debugging and suspiciousness ranking to isolate the corrupt assignment or logic error, propose a minimal patch, and generate a verifier-friendly test plan to confirm the fix.
Find the root cause of a failing test by running semantic codebase retrieval to locate the affected function, grep for suspect assignments or error strings, and read candidate files to identify the exact offending line.
Yes, you can use this approach for logic errors across multiple repositories where semantic codebase retrieval, grep, and targeted file reads are available to trace causal chains and deliver reliable fixes.
Structured debugging methods include backward reasoning, wolf fence, five whys, rubber duck narration, the scientific method, mental mutation, delta debugging, and suspiciousness ranking to trace causal chains to the exact line.
You should execute scripts during bug diagnostics only when deterministic automation is needed, prioritizing semantic codebase retrieval first, grep for exact pattern matches second, and file reads third.
CarlosQ96Detect hardcoded strings and build translation-ready JSON string tables.
robkamEnforce a red-green-proof loop starting with a failing regression test.
AvaTar-ArTsDiagnose and fix ToolUniverse tools with targeted tests and verification.
uukuguyApply binary search and trace-based debugging to diagnose code bugs.
