logdet-tracelisted
Install: claude install-skill vivekbhange-hub/log-detective-skill
# logdet-trace: from a wall of frames to one line of code
A trace has one frame that matters: the first line of your own code on the path to the root
cause. `trace_group.py` finds that frame in every trace in a log, groups traces that fail the
same way, and leaves the library and runtime frames out.
## Inputs
- A log containing traces, or a file holding one pasted trace (save it first; do not retype it).
- Where the service's source lives, so frames can be mapped to files. Ask if it is not the
current repository.
- The package or path prefixes that are "yours" (`src/`, `com.acme`, `app/`). Optional but
better: without them, any frame outside library, vendor and runtime paths counts as yours.
- Commands below say `python3`; on Windows use `python` (or `py -3`).
## Outputs
- `logs-triage/traces.md`: groups with counts, first and last seen, root-cause line, top three
application frames and one sample each.
- In chat: for the top groups, the mapped source location, a proposed cause, a confidence and
what would confirm it.
## Steps
1. **Confirm authorization.** The logs must come from a system the user owns or has permission
to examine. Do not help with traces from someone else's service.
2. **Group the traces:**
```
python3 "${CLAUDE_SKILL_DIR}/trace_group.py" app.log --app-prefix src/ --app-prefix com.acme \
--redact -o logs-triage/traces.md
```
`--app-prefix` is repeatable and matches the start of a path or function name, or a
directory in