Traces callers and dependents before editing shared code to map impact.
npx skills add https://github.com/ElliotJLT/Claude-Skill-Potions --skill trace-it
Please help me install this Agent Skill. Skill: trace-it Source: https://github.com/ElliotJLT/Claude-Skill-Potions/tree/main/skills/trace-it Command: npx skills add https://github.com/ElliotJLT/Claude-Skill-Potions --skill trace-it
Shared code changes can ripple across many call sites. This skill ensures you trace all callers and dependents before making edits, reducing regressions and unexpected breakages.
Run the trace-it process to map callers for a modified utility in utils/ or lib/ before patching.
High-intent search queries and answers about installing and using this skill.
Tracing callers maps all files that depend on a utility or library before you edit it. Run the trace-it process on the shared module to identify direct and indirect usages across 3+ files, revealing the full impact scope and preventing unintended breakages during refactoring.
Impact assessment visualizes affected modules by tracing all dependents of shared code. trace-it provides a complete dependency map showing which files import or use your target utility, enabling safe change planning and guiding reviewers through refactoring with minimal regression risk.
Enforce a structured change discipline by tracing all callers before touching shared utilities. trace-it identifies every file that depends on your module, creating an impact map that protects code by ensuring you plan changes systematically and communicate scope to reviewers.
Yes. trace-it enforces a change plan by listing all affected files and dependencies, making it ideal for reviewers who need to understand the blast radius. The dependency trace guides safe refactoring decisions and reduces the risk of overlooked call sites during code review.
Trace dependents when modifying utilities, libraries, or any module with multiple imports across 3+ files. This preparatory step activates whenever shared code changes to prevent unintended side effects, ensuring complete visibility into caller relationships before any edits.
Yes. Dependency tracing identifies both direct usages (modules that import your code) and indirect usages (modules that depend on modules importing your code). This complete caller map ensures no downstream impact is missed during refactoring.
23blocks-OSQuery a code graph database to analyze dependencies and change impact.
AZANIRAnalyze git diffs and commit history to recommend tests for execution, update, or creation.
yoanbernabeuGenerate recursive call graphs from GrepAI trace outputs with depth control.
yanochka11Finds code references, definitions, callers, imports across repositories using text, AST, or semantic search tools.
