Uses a local index to quickly gather relevant code context for tasks.
Install
mkdir -p .claude/skills/pruner && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/9584" && unzip -o skill.zip -d .claude/skills/pruner && rm skill.zipInstalls to .claude/skills/pruner
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Uses the local pruner indexer to gather relevant code context before making changes, debugging, refactoring, or answering questions about this repository.Key capabilities
- →Map code context
- →Build call graphs
- →Index symbols
How it works
It uses a pre-built tree-sitter index to provide immediate context on execution paths and dependencies.
Inputs & outputs
When to use pruner
- →Understanding dependencies before a refactor
- →Tracing execution paths for a bug fix
- →Getting context on a specific class or module
About this skill
Pruner — automatic code context
Pruner is a tree-sitter-based code indexer that pre-analyzes the entire codebase. It builds a call graph, symbol index, and file dependency map at index time, then uses your prompt keywords to find the most relevant execution paths, files, and code snippets. The output is equivalent to you running dozens of search and file-read calls, but computed in seconds from a pre-built index.
Before making code changes, fixing bugs, refactoring, or answering questions about this codebase:
- Get context:
pruner context /absolute/path/to/repo "<task description>"and read the output first. - Work directly from the output. Only read source files if a snippet is truncated or you need nearby lines.
- Use
--detailwhen brief pointers are not enough for tracing or debugging. - Do not re-explore the same query with grep, glob, or rg right after pruner.
When not to use it
- →Re-exploring with grep/rg after pruner
- →Reading source files when snippets suffice
Limitations
- →Requires pre-built index
How it compares
It provides pre-computed context in seconds, replacing dozens of manual search and file-read operations.
Compared to similar skills
pruner side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| pruner (this skill) | 0 | 3mo | No flags | Intermediate |
| ast-grep-find | 3 | 7mo | Review | Intermediate |
| framework-migration-code-migrate | 1 | 4mo | No flags | Advanced |
| effective-go | 323 | 9mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
ast-grep-find
parcadei
AST-based code search and refactoring via ast-grep MCP
framework-migration-code-migrate
sickn33
You are a code migration expert specializing in transitioning codebases between frameworks, languages, versions, and platforms. Generate comprehensive migration plans, automated migration scripts, and
effective-go
openshift
Apply Go best practices, idioms, and conventions from golang.org/doc/effective_go. Use when writing, reviewing, or refactoring Go code to ensure idiomatic, clean, and efficient implementations.
resolve-conflicts
antinomyhq
Use this skill immediately when the user mentions merge conflicts that need to be resolved. Do not attempt to resolve conflicts directly - invoke this skill first. This skill specializes in providing a structured framework for merging imports, tests, lock files (regeneration), configuration files, and handling deleted-but-modified files with backup and analysis.
solid-principles
SmidigStorm
Enforce SOLID principles (Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion) in object-oriented design. Use when writing or reviewing classes and modules.
dependency-upgrade
wshobson
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.