# Trace

> Trace how execution travels for one path — entry point through to the edges — to locate where behavior breaks.

- Skill: `chaitanya299/trace` (Agent Skill)
- Install (CLI): `npx skillmds@latest add chaitanya299/trace`
- Raw SKILL.md: https://api.skillmd.com/api/skills/chaitanya299/trace/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Chaitanya299 (https://skillmd.com/u/chaitanya299)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/chaitanya299/trace

---


# /orient:trace

Trace one execution path on demand, so you never have to maintain a flow doc that
goes stale the moment code changes.

Take a starting point from the user: a route, a CLI command, or a function. Dispatch
the `flow-tracer` agent with that starting point. Return the compact ordered path it
produces, with `file:line` references and the boundaries where control leaves the
codebase.

Write nothing to disk. If the user asks to save the trace, say that a saved flow doc
goes stale as soon as the code changes — that's why this traces on demand instead.