원클릭으로 Manus에서 모든 스킬 실행

tsa-deps

스타43

포크9

업데이트2026년 6월 16일 00:12

Dependency / import graph analysis. Answer "what does this file import", "what imports this module", "what's the project's import topology", "show me the sitemap" without reading every file's import block. Use when: - "What does file X depend on" / "what imports module Y" - "Is module Z a leaf or a hub in the import graph" - "Show me the project sitemap" (which files glue what together) - "Are there circular imports" - Planning a module extraction: who'd you break Replaces: grep-for-import-statements + manual graph walking (~5k tokens for non-trivial repos) with 1 MCP call (~500 tokens).

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

aimasteracc

aimasteracc/tree-sitter-analyzer

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

tsa-deps — Imports & module topology

Tool routing

Question	Tool
One file's direct deps	`health action=deps`
Project-wide import graph (who imports whom)	`health action=imports`
Project topology (entry points, hubs)	`structure action=sitemap`

Procedure

File-level deps

health action=deps file_path="tree_sitter_analyzer/ast_cache.py" mode="file_deps"
# returns: {imports: [...], imported_by: [...], depth: 2}

mode options:

summary — project-wide dependency summary (alias: full)
file_deps — one file's graph (requires file_path)
blast_radius — impact set for a file (alias: blast; requires file_path)
cycles — circular dependencies

Import graph (project-level)

health action=imports language="python" limit=50
# returns: ranked list of import hubs + leaves

Use to find:

Hubs (many things import this) — high blast radius if changed
Leaves (no one imports this) — possibly dead, or a CLI entry point
Cycles — circular imports needing breaking

Sitemap

structure action=sitemap
# returns: {entry_points: [...], hub_modules: [...], leaf_modules: [...]}

Useful as a "first look" right after tsa-landing.

CLI equivalents

uv run tree-sitter-analyzer <file> --dependencies file_deps
uv run tree-sitter-analyzer --dependencies summary
uv run tree-sitter-analyzer --import-graph --import-graph-mode summary
uv run tree-sitter-analyzer --codegraph-sitemap

Anti-patterns

DON'T grep for ^import / ^from to build a graph — incomplete (misses conditional / lazy imports captured by the AST)
DON'T worry about leaves at the start — they're often legitimate (CLI mains, examples). Focus on hubs.
DON'T extract a hub module without first checking its imported_by list — you'll break dozens of callers.

이 저장소의 다른 Skills

같은 저장소

tsa-find

aimasteracc/tree-sitter-analyzer

Fast file + content search with code-aware sizing. Replaces Read/Grep/find for routine "where is this file" / "grep for X" / "show me lines 10-20 of Y" questions. Returns file paths + line numbers + a sized chunk, not the whole file. Use when: - "Find files matching <pattern>" / "show me all *.yml under config/" - "Grep for 'TODO' / 'FIXME' / 'TODO\\(perf\\)' / regex anywhere" - "How big is <file>" / "is this file too large to read fully" - "Show me lines 50-80 of <file>" / "read just the relevant slice" - "Find all files matching name + containing string" Replaces: native find + grep + cat invocations (~3-10k tokens for big repos) with single MCP calls (200-500 tokens).

2026-06-1743

tsa-graph

aimasteracc/tree-sitter-analyzer

Code archaeology via call graph + symbol resolution. Answer "who calls X", "what does Y call", "where is Z defined", "what's the path from A to B" in one MCP call instead of multi-step grep + read. Uses persisted cross-file resolution (Synapse) so cross-module edges are precise, not regex-guessed. Use when: - User asks "what calls this function" / "what does this function call" - Tracing a bug through layers (impact → caller chain) - Planning refactor of a function/class (need full fanout) - "Where is this symbol defined" / "find all references to X" - "Show me the path from handler → DB" - "Draw a UML class/package/component/sequence diagram" Replaces: grep + read + manual chain-following (~10-30k tokens) with 2-4 MCP calls (~1-3k tokens).

2026-06-1743

tsa-index

aimasteracc/tree-sitter-analyzer

Manage the persistent AST cache / index. Refresh, force-rebuild, inspect cache state, diff one file's AST between commits, advise on parser readiness for a language. Mostly ops/infra, not daily agent work. Use when: - "Re-index the project" / "force rebuild AST cache" - "Why is callees returning unknown" (likely stale index) - "AST diff this file vs last commit" (structural diff, not text diff) - "What language plugins are ready / which are stubs" - Setting up the project for the first time (autoindex) Replaces: manual `rm -rf .ast-cache && reindex` + reading plugin docs.

2026-06-1743

tsa-refactor-queue

aimasteracc/tree-sitter-analyzer

Build a top-N prioritized refactoring queue by intersecting three signals: health grade (which files are F/D), temporal churn (which files change most often), and dead-code density (which files carry the most unreachable symbols). For each candidate the queue surfaces (a) the dimension that dragged the grade down, (b) the target symbol, (c) blast radius from `nav action=callers`, and (d) a concrete action — `split`, `delete dead`, or `extract`. Motivated by `docs/agent-tooling-gap-report.md` "Next High-Value Work" §5: use `health action=project` output to open focused refactoring slices for the current F-grade files, starting with low-coverage Language Plugin extractors and `api.py`. Use when: - "Where should I refactor next?" / "Build me a refactor queue" - Post-feature cleanup pass - Engineering planning: "what would 2 weeks of cleanup buy us?" - Re-grading after a sprint: "did the queue shrink?" Replaces: per-file `health action=file` loops + spreadsheet ranking (~25k tokens) with 3 parallel MCP calls +

2026-06-1743

tsa-temporal

aimasteracc/tree-sitter-analyzer

Find "hot zones" — symbols modified often in recent git history that need extra review attention. Adds temporal context (mod_count_30d / 90d / all) to call-graph queries. Like Hebbian "fire-together-wire-together" but for code: functions that change together often deserve scrutiny together. Use when: - User asks "what's churning the most" / "any hot zones?" - Pre-refactor: "what's the history of this function?" - Code review: "is this file getting hammered?" - You see a verdict=CAUTION with "hot zone" in risk_factors Replaces: `git log --follow --stat` + manual counting per-symbol (~10k tokens for non-trivial files) with 1 MCP call (~500 tokens).

2026-06-1743

tsa-edit-safety

aimasteracc/tree-sitter-analyzer

Pre-edit safety check using tree-sitter-analyzer. One workflow → verdict (SAFE/REVIEW/CAUTION/UNSAFE) + verification command + risk factors → ≤2k tokens, ≤3 MCP calls. Replaces ~10k tokens of grep/read/git-diff exploration before touching a file. Use when: - About to edit a file you haven't touched in this session - Refactoring across multiple files - Asked "is it safe to change X?" or "what breaks if I touch Y?" - Before approving a code review Workflow: 2-3 parallel MCP calls (edit action=safe + edit action=impact + health action=file), fold the verdicts, surface the exact `verification_command` and stop_condition.

2026-06-1643

name	tsa-deps
version	2.0.0
description	Dependency / import graph analysis. Answer "what does this file import", "what imports this module", "what's the project's import topology", "show me the sitemap" without reading every file's import block. Use when: - "What does file X depend on" / "what imports module Y" - "Is module Z a leaf or a hub in the import graph" - "Show me the project sitemap" (which files glue what together) - "Are there circular imports" - Planning a module extraction: who'd you break Replaces: grep-for-import-statements + manual graph walking (~5k tokens for non-trivial repos) with 1 MCP call (~500 tokens).
allowed-tools	["mcp__tree-sitter-analyzer__health","mcp__tree-sitter-analyzer__structure","Bash","Read"]

tsa-deps — Imports & module topology

Tool routing

Question	Tool
One file's direct deps	`health action=deps`
Project-wide import graph (who imports whom)	`health action=imports`
Project topology (entry points, hubs)	`structure action=sitemap`

Procedure

File-level deps

health action=deps file_path="tree_sitter_analyzer/ast_cache.py" mode="file_deps"
# returns: {imports: [...], imported_by: [...], depth: 2}

mode options:

summary — project-wide dependency summary (alias: full)
file_deps — one file's graph (requires file_path)
blast_radius — impact set for a file (alias: blast; requires file_path)
cycles — circular dependencies

Import graph (project-level)

health action=imports language="python" limit=50
# returns: ranked list of import hubs + leaves

Use to find:

Hubs (many things import this) — high blast radius if changed
Leaves (no one imports this) — possibly dead, or a CLI entry point
Cycles — circular imports needing breaking

Sitemap

structure action=sitemap
# returns: {entry_points: [...], hub_modules: [...], leaf_modules: [...]}

Useful as a "first look" right after tsa-landing.

CLI equivalents

uv run tree-sitter-analyzer <file> --dependencies file_deps
uv run tree-sitter-analyzer --dependencies summary
uv run tree-sitter-analyzer --import-graph --import-graph-mode summary
uv run tree-sitter-analyzer --codegraph-sitemap

Anti-patterns

DON'T grep for ^import / ^from to build a graph — incomplete (misses conditional / lazy imports captured by the AST)
DON'T worry about leaves at the start — they're often legitimate (CLI mains, examples). Focus on hubs.
DON'T extract a hub module without first checking its imported_by list — you'll break dozens of callers.