Reproduce software failures and isolate root causes with read-only tools.
npx skills add https://github.com/automagik-dev/genie --skill trace-automagik-dev
Please help me install this Agent Skill. Skill: trace Source: https://github.com/automagik-dev/genie/tree/main/skills/trace Command: npx skills add https://github.com/automagik-dev/genie --skill trace-automagik-dev
This Skill provides a systematic approach to investigating and diagnosing the root cause of unknown software failures when the source of the problem is not immediately apparent.
/trace to have an agent meticulously investigate, reproduce the bug, trace its execution path, and provide a clear report on the root cause, ready for the /fix skill.Use the trace skill to investigate the authentication bug reported in the login flow.
High-intent search queries and answers about installing and using this skill.
To find the root cause of a software failure, you need a systematic approach to gather symptoms, reproduce the issue, and trace the execution path to isolate where it originates. This produces a structured report detailing evidence and a recommended correction.
Debugging a cryptic error message involves autonomously reproducing the reported issue to ensure consistent understanding, then following the execution flow to pinpoint the exact failure point. This isolates the fundamental reason behind the bug for a structured handoff.
Automated bug investigation in a read-only environment works by dispatching a specialized agent to read files, execute bash commands, and search codebases. It investigates in isolation without modifying the system to safely isolate the failure point.
Yes, you can trace an execution path without modifications by operating in a read-only environment. The investigation uses tools like Read, Bash, Glob, and Grep to gather evidence and map the causal chain safely without altering system state.
To reproduce a reported issue for root cause analysis, you need the reported symptoms and access to the codebase. The investigation isolates the problem autonomously, ensuring a consistent understanding before tracing the failure origin.
You should use a dedicated tracing tool when a critical bug is reported but the source is not immediately apparent. It meticulously investigates, reproduces the bug, and outputs a structured report ready for a fixing agent to apply corrections.
jonkikyTrace reported issue symptoms to code paths and verify root cause hypotheses.
BordaDiagnose unknown failures by collecting signals and ranking hypotheses.
duggal1Identify and remediate software errors using a structured debugging workflow with verified tool outputs.
mikeyobrienDispatch parallel agents to investigate independent failures across files or subsystems.