Run focused `kit` CLI commands (file-tree, symbols, search, semantic discovery, dependency analysis, and exports) to build high-signal repository context fast. Use when you need to understand an unfamiliar codebase, prep context for Claude, plan refactors, audit dependencies, or answer “where is X implemented?” without manually grepping.
85
82%
Does it follow best practices?
Impact
81%
3.85xAverage score across 3 eval scenarios
Passed
No known issues
Codebase onboarding brief via baseline snapshot and search
File-tree to debug/
0%
100%
Symbols extracted
0%
100%
Literal search used
0%
100%
Semantic search used
0%
0%
Literal before semantic
0%
0%
Absolute path in commands
0%
100%
Command log structure
100%
100%
Output stored in debug/
0%
100%
file-content command used
0%
100%
kit context or chunk-symbols used
0%
100%
Symbol usage audit and refactor prep with kit usages and context
kit usages command
0%
100%
kit usages --type flag
0%
0%
kit symbols --format json
0%
100%
Usages output saved
0%
100%
kit context or chunk-symbols
0%
100%
No full file pastes
100%
100%
Outputs in debug/
0%
100%
Absolute path in commands
100%
100%
Command log exit status
100%
100%
Command log key findings
100%
100%
Python dependency graph and cycle detection with kit dependencies and kit index
kit dependencies used
0%
100%
Python language flag
0%
100%
Structured output format
0%
100%
Cycles flag used
0%
100%
Dependency output in debug/
0%
0%
kit index used
0%
50%
kit cache warm used
0%
0%
Circular deps reported
100%
100%
Absolute path in commands
0%
100%
Command log exit status
100%
100%
a026516
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.