# Quick Lineage

> Show a colored call graph in chat, fast — no files, no viewer, no gate. Use when the user wants to see the call graph or flow of a function, command, or object under discussion; after changes land, to show what they did to the flow; or before making changes, to show what you are about to do to it.

- **Type:** Skill
- **Install:** `agentstack add skill-yassimba-loom-quick-lineage`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [Yassimba](https://agentstack.voostack.com/s/yassimba)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** Apache-2.0
- **Upstream author:** [Yassimba](https://github.com/Yassimba)
- **Source:** https://github.com/Yassimba/loom/tree/main/skills/quick-lineage

## Install

```sh
agentstack add skill-yassimba-loom-quick-lineage
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Quick Lineage

One colored call graph in chat, grounded in `stackdiff` (AST-verified for TS/TSX, Python, Go, Rust) — the fast sibling of **lineage** and **blueprint**, for when the picture matters more than the ceremony.

## 1. Read the branch from the conversation

Infer both the **entry** (the function, command, or object's method the conversation centers on — with several candidates, the one whose call tree covers the most of what was discussed) and the **branch**:

- **Discussed** — the user is asking about something as it is → one world, current source.
- **Landed** — changes exist (session edits, working tree, a named ref) → diff the worlds.
- **Planned** — the change is still intent → real BEFORE rails plus a projected `±` overlay.

State the choice in one line ("quick lineage of `run`, landed changes vs HEAD") before running anything. Done when: the entry and branch are named in chat — silently picking is how the wrong graph gets drawn.

## 2. Run stackdiff

Start at `--max-depth 2` and deepen only the limb the question lives in — full depth buries the point.

| Branch | Command |
| --- | --- |
| Discussed | `stackdiff --tree -e  --max-depth 2 --format markdown` (add `` for a past world) |
| Landed | `stackdiff  -e  --max-depth 2 --only-changes --format markdown` — working tree included; add `` for ref-to-ref |
| Planned | the Discussed command for BEFORE rails, then hand-write `+`/`-` lines for the intended calls |

`--format markdown` emits the ```` ```diff ```` fence ready to paste; rich mode annotates each node with `binding = call(args) → return`, its doc line, and `path:line`. Unchanged limbs trim to `…` by default (widen with `--context N`, `--full` for everything). When the question is convergence — "do these paths reach the same thing?" — use `--view lineage`: the call DAG at data granularity, each function drawn once with fan-in visible, data objects as stadium nodes, bindings riding the edges.

Entry not found → `stackdiff --tree` lists the exported entrypoints; pick the nearest and say you did. Language outside TS/TSX/Python/Go/Rust → say stackdiff cannot parse it and trace by hand, marked as unverified. "Who calls X" questions → `--callers -e X` inverts the graph.

### Tuning noise

Builtin/plumbing calls (`len()`, `clone()`, `str()`, `println!`) hide by default so the graph is your code talking to your code. When a graph still reads cluttered, tighten it in one loop: run `stackdiff --noise-report` (a frequency table of unresolved calls, marked `hidden`/`shown`), add `hide = ["glob", …]` globs for the framework plumbing you see to `.stackdiff.toml` at the repo root (`show = […]` rescues false positives), and re-run. `--noise` reveals everything when you suspect the filter ate signal.

## 3. Show it colored

Paste the markdown output as-is — the ```` ```diff ```` fence renders `+` green and `-` red (`!` marks a same-call-different-arguments change), and the two-space status column keeps rails aligned. For **Planned**, projected lines are the design's promise, not source facts — say so above the block.

Under the block, one takeaway sentence: what the graph shows about the question that prompted it.

Done when: the graph is in chat with every `+`/`-` line either machine-verified by stackdiff or explicitly marked projected, and the takeaway names what changed or will change.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [Yassimba](https://github.com/Yassimba)
- **Source:** [Yassimba/loom](https://github.com/Yassimba/loom)
- **License:** Apache-2.0

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-yassimba-loom-quick-lineage
- Seller: https://agentstack.voostack.com/s/yassimba
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.