cqs-impact

Name: cqs-impact
Availability: InStock
Author: jamie8johnson

List callers and affected tests for a function change using reverse BFS.

13|3|Updated Jan 31, 2026

Search Tags:#debugging #tests #code-change #callers #impact-analysis #reverse-bfs #mcp-tool

Ready to run

npx skills add https://github.com/jamie8johnson/cqs --skill cqs-impact

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cqs-impact
Source: https://github.com/jamie8johnson/cqs/tree/main/.claude/skills/cqs-impact
Command: npx skills add https://github.com/jamie8johnson/cqs --skill cqs-impact

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly assess the impact of code changes by identifying which call sites and tests would be affected when a function changes.

Core Features & Use Cases

Caller-aware impact analysis: discover direct and indirect callers of a function with contextual snippets.
Test impact visibility: surface the tests that exercise the affected call paths.
Efficient workflows: leverages reverse BFS to consolidate multiple steps into a single analysis pass.

Quick Start

Run cqs_impact with the target function name to analyze, optionally specifying --depth to limit caller traversal.

Frequently Asked Questions about cqs-impact

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

FAQPage Schema

How do I identify callers and affected tests when changing a function?▼

To identify callers and affected tests when changing a function, you can run a reverse BFS impact analysis. This process traces the call graph to list direct and indirect call-site snippets and surfaces the tests exercising those paths.

What is reverse BFS for code impact analysis?▼

Reverse BFS for code impact analysis is a traversal method that maps the ripple effects of code changes. It walks backward through the call graph to consolidate direct and indirect caller identification with affected test discovery into a single pass.

How do I limit the depth of caller traversal during impact analysis?▼

You can limit the depth of caller traversal during impact analysis by specifying a depth parameter. This restricts the reverse BFS traversal, ensuring the analysis only maps call-site snippets up to the specified depth boundary.

Does impact analysis work with MCP-based codebases?▼

Yes, impact analysis works specifically with MCP-based codebases. It is designed to understand ripple effects across a call graph and tests within environments that support MCP tool integration.

Can I see call-site snippets when analyzing code change impact?▼

Yes, you can see call-site snippets when analyzing code change impact. The analysis returns contextual code snippets for both direct and indirect callers discovered during the reverse BFS traversal.