Trace code change impacts on business capabilities via LSP call chains.
npx skills add https://github.com/xxsoul/skills-code-tracer --skill code-impact-tracker
Please help me install this Agent Skill. Skill: code-impact-tracker Source: https://github.com/xxsoul/skills-code-tracer/tree/main Command: npx skills add https://github.com/xxsoul/skills-code-tracer --skill code-impact-tracker
Track code changes' impact on business scope by tracing the call chain through an LSP server. It enables answering questions like "what does this function affect" and "which APIs call this code", and it supports generating impact reports with git commit references.
Provide a starting point (file:line, commit, or function) and the tool will perform an LSP trace and produce both Markdown and JSON reports.
High-intent search queries and answers about installing and using this skill.
To trace code changes to business impact, you resolve symbols and trace call hierarchies using an LSP server. This identifies affected business entry points and produces structured Markdown and JSON impact reports.
The best way to identify affected APIs is by tracing the downstream call chain from the modified function using LSP. This maps the code change to business entry points like API paths to reveal the full impact scope.
Code impact analysis works across any language that has an active LSP server implementation. The tool orchestrates language-agnostic symbol resolution and call hierarchy tracing to deliver consistent impact reports.
To generate commit-referenced impact reports, you provide a git commit or file:line starting point for the trace. The tool outputs both Markdown and JSON reports linking the analyzed code changes to the business impact.
Yes, you can map downstream effects from schedulers and config-driven paths. The LSP-backed call chain tracing identifies these business entry points and maps their downstream impact across software modules.
A limitation of using LSP for call chain tracing is that it requires an active LSP server for the target language. Without active LSP support, the tool cannot perform symbol resolution or trace the call hierarchy.
blackwell-systemsAnalyze source files to list symbols, highlight usages, and retrieve type info.
Eric-Pacheco95Generate Markdown release notes from merged pull requests, closed tickets, and commit history.
blackwell-systemsDetermine the blast radius of a symbol or file via references, callers, and type relationships.
tianzecnDiagnose bug root causes via AST-based call-chain analysis with claudemem v0.3.0.
