Nexus-skills

왜 쓰나요

핵심 기능

Persistent .nexus-map/ knowledge base per repo
File structure, dependency graph, import + call-site tracking
Change-impact radius queries
Incremental updates — re-run only on changed files
Tool-calling LLMs consume the map to answer precise questions
Works with Copilot, Cursor, Claude Code, and generic agents

라이브 데모

실제 사용 모습

nexus-skill.replay ▶ 준비됨

0/0

설치

작성자 저장소 · Claude Skills 공식 문서

사용 사례

실전 활용법: Nexus-skills

How to onboard to an unfamiliar codebase fast

👤 Engineers joining a new team or team inheriting a codebase ⏱ ~60 min intermediate

언제 쓸까: Day one in a repo you've never seen; you want a map before making changes.

흐름

Build the map

Use nexus-skills to scan this repo and build .nexus-map/.✓ 복사됨

→ Progress output + map files produced
Get the tour

Using .nexus-map, tell me: entry points, top 10 most-imported modules, and any orphaned files.✓ 복사됨

→ Repo overview keyed to actual files
Dig into a subsystem

Show me the payments subsystem — files, dependencies, external calls.✓ 복사됨

→ Scoped subsystem view

결과: A factual mental model of the repo built in under an hour.

함정

Map goes stale after big merges — Re-run nexus update; it's incremental

Check blast radius before changing a core function

👤 Engineers about to touch a widely-used utility ⏱ ~30 min intermediate

언제 쓸까: You're about to rename or change the signature of a function and want to see every call site.

사전 조건

.nexus-map/ already built — Run once per repo; incremental after

흐름

Query impact

What calls formatCurrency(), and what would break if I change the signature to accept a locale?✓ 복사됨

→ Call-site list with each caller's likely break mode
Generate migration

Produce the minimal diff across all call sites to add the new locale param with a sensible default.✓ 복사됨

→ Multi-file patch

결과: A change with known blast radius and a prepared diff.

Find dead code and unused exports

👤 Engineers cleaning up before a refactor ⏱ ~40 min intermediate

언제 쓸까: Before a refactor you want to know what's truly unused.

흐름

Query map

Using .nexus-map, list files with no imports from elsewhere, and exports with no external references.✓ 복사됨

→ Ranked list with confidence per finding
Verify

For the top 10 candidates, double-check by searching for string-based usage (reflection, dynamic imports).✓ 복사됨

→ Filtered list with false-positive caveats

결과: A dead-code delete list you can actually ship.

함정

Dynamic imports look dead statically — Always run the string-based sweep before deleting

조합

다른 MCP와 조합해 10배 효율

nexus-skill + claude-code-owasp-skill

Security-impact queries: where does tainted input flow?

Using nexus-map, trace every call path from the /ingest endpoint into the DB layer. Then OWASP review those paths.✓ 복사됨

도구

이 MCP가 노출하는 것

도구	입력	언제 호출	비용
build_map	repo_root	Once per repo initially	compute (local)
update_map	changed_files	After large merges	compute (local)
query_structure	question	Answering structure questions	Claude tokens
change_impact	symbol or file	Before breaking changes	Claude tokens
dead_code	-	Pre-refactor cleanup	Claude tokens

비용 및 제한

운영 비용

API 쿼터: None
호출당 토큰: Map build is local compute (fast); queries consume Claude tokens
금액: Free
팁: Build once, query often. Re-build only when repo shape changes materially.

보안

권한, 시크릿, 파급범위

자격 증명 저장: No credentials. .nexus-map/ is local by default.

데이터 외부 송신: Map building is local. Querying sends map snippets to Claude.

Add .nexus-map/ to .gitignore unless your team agrees to share it — it's a detailed map of the codebase.

문제 해결

자주 발생하는 오류와 해결

Map build crashes on monorepos

Run per-package rather than on the root; nexus supports a scope flag

Queries return stale results after edits

Run nexus update on the changed files; incremental is cheap

Language not recognized

Check supported languages in nexus docs; some frameworks need explicit parser config

대안

Nexus-skills 다른 것과 비교

대안	언제 쓰나	단점/장점
SourceGraph / Cody	You need hosted code intelligence at org scale	Paid; not local
tree-sitter + custom queries	You want full control	Much more build time