See which project docs your AI actually discovers.
- Local and dependency-free: no cloud, analytics, or model tokens.
- Separate heat, lifetime reads, searches, and untouched paths instead of guessing intent.
- Reduce the evidence to an A–F documentation health grade when detail is unnecessary.
Documentation steers an AI coding assistant toward your team’s patterns and guardrails. But a rule that is never read protects nothing. trigger-tree records discovery evidence so you can improve the routes without pretending a read proves understanding.
| Claude Code | Codex |
|---|---|
/plugin marketplace add Hedde/trigger_tree/plugin install trigger-tree@trigger-tree/reload-plugins/tt watch demo/tt setup · /tt doctorWork normally, then /tt insights |
codex plugin marketplace add Hedde/trigger_treecodex plugin install trigger-treeRestart Codex Ask it to run python3 "$PLUGIN_ROOT/scripts/tt-watch.py" --demoUse the bundled trigger-tree skill for setup, doctor, and insights |
The Claude /tt skill is explicitly user-triggered. Codex installs the equivalent skill and lifecycle hooks through its plugin marketplace.
Prefer a standalone CLI — for CI, git-hook ingestion, or dashboards without a plugin?
pipx install trigger-tree (or uvx --from trigger-tree tt), then tt doctor, tt watch --demo, tt stats.
Prompt logging defaults to a recognizable, gitignored local preview of at most 200
characters as soon as the plugin is installed, even if setup is never run. /tt setup
asks whether to keep truncate or switch future events to hash or off.
| You are… | trigger-tree gives you… |
|---|---|
| Senior developer | File/folder heat, search evidence, router gaps, and prompt-level browsing |
| Tech lead | Trends, task clusters, protected-context review, and evidence-backed fixes |
| Product owner | One honest A–F docs-health signal, provisional until measurement matures |
| Command | Result |
|---|---|
/tt watch demo |
Instant synthetic dashboard; no telemetry required |
/tt setup [truncate|hash|off] |
Wire the repo and choose prompt privacy |
/tt doctor |
Check hooks, liveness, scope, privacy, and statusline wiring |
/tt status |
Current heat, lifetime reads, and untouched paths |
/tt watch |
Live mock-TUI dashboard with prompt browsing and sorting |
/tt insights |
Deterministic analysis plus a local HTML report |
/tt suggestions |
Up to five evidence-backed routing improvements |
/tt badge |
Write a public-safe docs-health endpoint JSON |
/tt note <text> |
Add a local timeline annotation |
/tt uninstall |
Remove wiring without deleting telemetry |
Search telemetry is a conservative lower bound; see measurement boundaries.
- Hooks log shell-side to the gitignored
.trigger-tree/history.jsonl; failures never interrupt the coding session. - A deterministic aggregator computes every metric with Python’s standard library; the model interprets but never counts.
- Discovery remains model-driven: trigger-tree measures your routers and reads without injecting context or changing routing.
| Category | Question answered |
|---|---|
| Token/trace observability (Langfuse, Arize, W&B) | What did the model call, spend, and produce? |
| Documentation linters | Is documentation structurally or stylistically valid? |
| trigger-tree | Which local project docs did the coding assistant actually discover? |
The categories complement each other. trigger-tree does not evaluate answer quality or claim that a read caused an outcome.
Documentation router · Dashboard · Heat model · Configuration · Privacy · Glossary · FAQ · Website · Changelog
MIT © Hedde van der Heide