| name | graphyn |
| description | Use Graphyn for symbol impact analysis, dependency lookup, usages, aliases, and property-level access before modifying code. |
Graphyn Skill
Use this skill when the task involves changing, deleting, renaming, moving, or understanding a code symbol.
Workflow
- Ensure the graph exists with
graphyn analyze . or the refresh_graph MCP tool.
- For changes to a symbol, inspect blast radius.
- For deletion or rename, inspect usages.
- For moving or extracting code, inspect dependencies.
- Mention high-risk findings before editing.
Commands
graphyn query blast-radius SymbolName
graphyn query usages SymbolName
graphyn query deps SymbolName
If symbols are missing because files are ignored or filtered out:
graphyn analyze . --no-gitignore
graphyn analyze . --include "src/**/*.ts"
graphyn analyze . --exclude "tests/**"
When MCP is available, prefer:
get_blast_radius
get_symbol_usages
get_dependencies
refresh_graph
refresh_graph can receive path, respect_gitignore, include, and exclude.
Reading Results
- Aliases are real usages, even if text search misses them.
properties_accessed matters for DTO/model field changes.
- Use
--file path/to/file.ts if a symbol name is ambiguous.