code-review-graph-debug

Trace bug root cause and impact using a code-review knowledge graph.

51|6|Updated Mar 10, 2019
One-click install
npx skills add https://github.com/AniTrend/anitrend-v2 --skill code-review-graph-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-graph-debug
Source: https://github.com/AniTrend/anitrend-v2/tree/main/.agents/skills/code-review-graph-debug
Command: npx skills add https://github.com/AniTrend/anitrend-v2 --skill code-review-graph-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates guesswork during code reviews by helping you trace a bug’s origin and understand its downstream impact using a code-review knowledge graph.

Core Features & Use Cases

  • Systematic call-chain tracing: Identify relevant nodes, then follow callers and callees to reconstruct how control flows into and out of the suspected area.
  • Execution-path visibility: Use flow views to see full execution paths through the affected components when graph navigation is not enough to explain behavior.
  • Change-impact assessment: Detect whether recent changes correlate with the issue and estimate an impact radius across related files.
  • Use Case: When a new crash or regression appears in AniTrend after a recent commit, use the graph to locate the exact entry point, trace the failing call chain, and determine which components are likely affected.

Quick Start

Use the code-review-graph-debug skill to trace a suspected bug by following minimal-context orientation, semantic node search, caller/callee graph traversal, execution-flow inspection, change detection, and impact-radius assessment.

Frequently Asked Questions about code-review-graph-debug

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

FAQPage Schema
How do I trace a bug through a call graph during a code review?

Trace a bug through a call graph by performing semantic node searches and following caller/callee relationships to reconstruct execution flow. This method locates the exact entry point of a regression and identifies affected components across the codebase.

What is impact analysis and how does it estimate an impact radius after recent changes?

Impact analysis detects whether recent code changes correlate with a new issue and evaluates the impact radius across related files. It determines which downstream components are likely affected by tracing the execution path from the modified nodes.

How do I debug a regression by reconstructing a failing call chain?

Debug a regression by reconstructing a failing call chain through minimal-context orientation and graph traversal. Query callers and callees of suspected nodes to systematically trace how control flows into and out of the affected area.

When should I use execution flow inspection instead of call graph navigation for debugging?

Use execution flow inspection for debugging when standard call graph navigation is not enough to explain behavior. Flow views provide full execution-path visibility through affected components, showing detailed control flow beyond basic caller and callee links.

What is the best way to find the root cause of a crash after a recent commit?

Find the root cause of a crash after a recent commit by using change detection to correlate the issue with recent modifications. Trace the failing call chain backward from the crash point to pinpoint the exact origin of the regression.