cqs-trace

Find the shortest call path between two functions using BFS.

13|3|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/jamie8johnson/cqs --skill cqs-trace
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cqs-trace
Source: https://github.com/jamie8johnson/cqs/tree/main/.claude/skills/cqs-trace
Command: npx skills add https://github.com/jamie8johnson/cqs --skill cqs-trace

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the analysis of codebases by revealing the shortest path between two functions in a call graph, enabling faster debugging and understanding of dependencies.

Core Features & Use Cases

  • BFS-based shortest path discovery between source and target functions
  • Returns step-by-step path with file, line, and function signatures
  • Useful for debugging, code comprehension, and impact analysis across modules

Quick Start

Run the cqs_trace tool with a source and target function to obtain the BFS path.

Frequently Asked Questions about cqs-trace

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

FAQPage Schema
How do I find the shortest function call path between two functions in a codebase?

To find the shortest function call path, this Skill uses breadth-first search (BFS) to map the call graph and return the step-by-step path with file, line, and function signatures. It automates dependency analysis.

Can I trace function call relationships across different modules for debugging?

Yes, you can trace function call relationships across modules for debugging. The BFS-based path discovery reveals dependencies between a source and target function, returning the exact file and line details.

How does BFS help with code navigation and impact analysis?

BFS helps with code navigation by systematically exploring the function call graph to guarantee the shortest connection. This reveals direct dependencies and step-by-step execution paths for accurate impact analysis.

What do I need to provide to trace a function call path?

To trace a function call path, you need to provide a source function and a target function. The tool parses these arguments and outputs the formatted BFS path with file, line, and signature details.

What is the best way to understand function dependencies without manually reading the entire codebase?

The best way to understand function dependencies is to automate call graph analysis with BFS. This reveals the shortest path and step-by-step signatures between functions, bypassing the need to manually read code.

Does this path tracing approach work for large software engineering projects?

This path tracing approach works for software engineering projects where function call relationships are defined. It returns the shortest BFS path, though complex highly dynamic calls may limit static graph accuracy.