skills.rest
arpitarya
arpitaryaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

fux-trace

Traverse a knowledge graph to explain how a feature spans modules.

1|Updated Jun 1, 2026
Search Tags:#knowledge graph#code exploration#call graph#cross-module#graph traversal#fux#feature trace
One-click install
npx skills add https://github.com/arpitarya/fux --skill fux-trace-arpitarya
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fux-trace
Source: https://github.com/arpitarya/fux/tree/main/archive/v0.1/fux/data/skills/trace
Command: npx skills add https://github.com/arpitarya/fux --skill fux-trace-arpitarya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Understanding how a feature or concept cuts across multiple modules usually means grepping for string matches and manually piecing together relationships. This Skill walks a pre-built graph of rules, files, symbols, and call edges to explain cross-module behavior by traversal instead of repeated searching. ## Core Features & Use Cases - Graph Anchoring: Locates entry points by recalling governing rules and matching node labels in the graph file. - Edge Traversal: Follows governs, contains, calls, related, and depends-on edges to trace data and control flow across modules. - Cited Explanation: Narrates the path module-by-module with path:line citations and rule references, distinguishing extracted edges from inferred ones. - Use Case: Ask how "day P&L" flows through the system, and receive a module-by-module explanation grounded in real call edges and governing rules rather than grep results. ## Quick Start Run /fux trace "day P&L" to explain how that feature spans modules using the project graph.

Frequently Asked Questions about fux-trace

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I trace how a feature spans multiple modules?▼

Run /fux trace with the feature name, such as /fux trace "day P&L". The workflow anchors on governing rules and graph nodes, then walks governs, contains, and calls edges to narrate the path module-by-module with path:line citations.

Why use graph traversal instead of grep for code exploration?▼

Grep finds string matches, while the graph encodes relationships: which rule governs which file, which function calls which, and which decision constrains which module. Traversal answers how X relates to Y without re-scanning files each time.

What do I need before running a graph trace?▼

You need the fux engine installed and a current graph built with fux build, which produces the graph.json file the trace walks. Without a current graph, anchors and edges may be stale or missing.

Does the trace distinguish real call edges from inference?▼

Yes. The explanation step explicitly separates what the graph extracted, meaning real call edges, from what the narrator inferred during traversal, so you can trust the cited hops.

Can a trace improve future graph queries?▼

Yes. If a trace surfaces an undocumented cross-module rule, you can capture it with fux new rule so the next trace starts from richer graph knowledge.

Related Skills

Explore More Software Engineering Skills→
yusaduymazyusaduymaz

gsd-graphify

Build and inspect repository knowledge graphs with queryable node summaries.

Community
Advanced
sam-fakhreddinesam-fakhreddine

wfc-sync

Syncs project docs and AI agent configs with actual repository state.

Community
Advanced
SermilionSermilion
13

bill-boundary-decisions

Capture architectural decision rationale in a module's decisions.md file.

Community
Advanced
pv-udpvpv-udpv

code-analysis

Parse source code into ASTs, dependency graphs, and knowledge graphs.

Community
Advanced