smart-context

Extract relevant context from codebase graphs using level-based queries.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/monicajeon28/GMcruise --skill smart-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smart-context
Source: https://github.com/monicajeon28/GMcruise/tree/main/.claude/skills/smart-context
Command: npx skills add https://github.com/monicajeon28/GMcruise --skill smart-context

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

코드베이스 전체를 읽어 필요한 맥락을 빠르게 얻기 어렵고, 불필요한 정보로 토큰이 낭비되는 문제를 해결합니다. codebase-graph 기반으로 필요한 컨텍스트만 선택적으로 추출합니다.

Core Features & Use Cases

  • 컨텍스트 레벨 기반 추출: Level_0 ~ Level_4까지 필요한 정보만 선택적으로 로드
  • 코드베이스 그래프에서 시그니처, 호출 관계, 의존성 등을 정확히 식별
  • 토큰 절감과 정확도 향상을 위한 부분 로딩 전략

Quick Start

target 함수/클래스가 어디에서 사용되는지 파악하기 위해 codebase-graph를 사용해 관련 노드들만 로드합니다.

Frequently Asked Questions about smart-context

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce token usage when analyzing code dependencies and references?

Extract only relevant context from your codebase graph instead of loading entire files. Smart Context applies graph-based filtering on signatures, references, and dependencies to achieve ~72% token savings while maintaining ~92% accuracy, using configurable depth levels (0-5) and relation scopes.

What is context-level extraction and how does it work with codebase graphs?

Context-level extraction selectively loads information at different depths—Level 0 through Level 5—from a codebase graph. This strategy identifies only signatures, call relationships, and dependencies relevant to your target function or class, minimizing unnecessary token consumption.

Can I use partial loading to understand where a function is called across my codebase?

Yes. Query the codebase graph to load only related nodes showing where your target function or class is referenced. This partial loading strategy reveals call chains and dependencies without loading entire files, saving tokens and focus.

What token savings and accuracy can I expect from selective context extraction?

Selective extraction from codebase graphs delivers approximately 72% token reduction with around 92% accuracy. Results depend on configuring appropriate depth levels and relation scopes to match your analysis scope.

Do I need to set up a codebase graph before using context extraction?

Yes. Smart Context requires a codebase-graph as input—a prerequisite that maps signatures, references, and dependencies across your project. This graph structure enables the selective, token-efficient extraction of relevant context.

What's the difference between extracting Level 0 versus Level 5 context?

Level 0 captures minimal direct information; higher levels (up to Level 5) progressively include related signatures, transitive dependencies, and call chains. Adjust depth to balance token budget against comprehensiveness for your analysis task.