Impact

Name: Impact
Author: Project-SandStar

ASecurity

Blast radius of a symbol before you change it - callers, depth, affected files (getCallers + getCodeImpact). Usage - /fantom-mcp:impact connExt::ConnTuning.pollTime

2 stars
0 votes
0 copies
0 views
Added October 19, 2026

ai-agents

Works with

Security analysis

A100/100

Scanned October 19, 2026

npx -y skills add Project-SandStar/FantomMcpServer --skill impact --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Impact?

Add the live security badge to your README. It updates with every re-scan.

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/project-sandstar-impact/badge)](https://www.skillsdirectory.com/skills/project-sandstar-impact)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: impact
description: Blast radius of a symbol before you change it - callers, depth, affected files (getCallers + getCodeImpact). Usage - /fantom-mcp:impact connExt::ConnTuning.pollTime
argument-hint: <qualifiedName like pod::Type.method>
---

Find what depends on this symbol before anyone edits it:

> $ARGUMENTS

Steps:

1. `ToolSearch("fantom", 30)` if the Fantom tools are not loaded yet.
2. Take the `projectId` from the session context. If the argument is not a
   full qualified name, resolve it first with `searchFantomCode` (`query` =
   the argument, that `projectId`) and use the best match.
3. Call `getCallers` (`qualifiedName`, `projectId`, `maxDepth: 3`).
4. Call `getCodeImpact` (`qualifiedName`, `projectId`).
5. Report a short list: direct callers (file:line), callers of callers, and
   the files that a change would touch. Mark test files separately. End with
   one line: safe to change, or needs care, and why.