⚡ PRIMARY TOOL for semantic code search AND structural analysis. NEW: AST tree navigation with map, symbol, callers, callees, context commands. PageRank ranking. ANTI-PATTERNS: Reading files without mapping, Grep for 'how does X work', Modifying without caller analysis.
⚡ PRIMARY TOOL for semantic code search AND structural analysis. NEW: AST tree navigation with map, symbol, callers, callees, context commands. PageRank ranking. ANTI-PATTERNS: Reading files without mapping, Grep for 'how does X work', Modifying without caller analysis.
allowed-tools
Bash, Task, AskUserQuestion
Claudemem Semantic Code Search Expert (v0.6.0)
This Skill provides comprehensive guidance on leveraging claudemem v0.7.0+ with AST-based structural analysis, code analysis commands, and framework documentation for intelligent codebase understanding.
v0.3.0 adds AST tree navigation with symbol graph analysis:
PageRank ranking - Symbols ranked by importance (how connected they are)
Call graph analysis - Track callers/callees for impact assessment
Structural overview - Map the codebase before reading code
Quick Reference
# Always run with --nologo for clean output
claudemem --nologo <command>
# Core commands for agents
claudemem map [query] # Get structural overview (repo map)
claudemem symbol <name> # Find symbol definition
claudemem callers <name> # What calls this symbol?
claudemem callees <name> # What does this symbol call?
claudemem context <name> # Full context (symbol + dependencies)
claudemem search <query> # Semantic search with --raw for parsing
claudemem search <query> --map # Search + include repo map context
Version Compatibility
Claudemem has evolved significantly. Check your version before using commands:
claudemem --version
Command Availability by Version
Command
Minimum Version
Status
Purpose
map
v0.3.0
✅ Available
Architecture overview with PageRank
symbol
v0.3.0
✅ Available
Find exact file:line location
callers
v0.3.0
✅ Available
What calls this symbol?
callees
v0.3.0
✅ Available
What does this symbol call?
context
v0.3.0
✅ Available
Full call chain (callers + callees)
search
v0.3.0
✅ Available
Semantic vector search
dead-code
v0.4.0+
⚠️ Check version
Find unused symbols
test-gaps
v0.4.0+
⚠️ Check version
Find high-importance untested code
impact
v0.4.0+
⚠️ Check version
BFS transitive caller analysis
docs
v0.7.0+
✅ Available
Framework documentation fetching
Version Detection in Scripts
# Get version number
VERSION=$(claudemem --version 2>/dev/null | grep -oE '[0-9]+\.[0-9]+\.[0-9]+' | head -1)
# Check if v0.4.0+ features availableif [ -n "$VERSION" ] && printf'%s\n'"0.4.0""$VERSION" | sort -V -C; then# v0.4.0+ available
claudemem --nologo dead-code --raw
claudemem --nologo test-gaps --raw
claudemem --nologo impact SymbolName --raw
elseecho"Code analysis commands require claudemem v0.4.0+"echo"Current version: $VERSION"echo"Fallback to v0.3.0 commands (map, symbol, callers, callees)"fi
Graceful Degradation
When using v0.4.0+ commands, always provide fallback:
# Try impact analysis (v0.4.0+), fallback to callers (v0.3.0)
IMPACT=$(claudemem --nologo impact SymbolName --raw 2>/dev/null)
if [ -n "$IMPACT" ] && [ "$IMPACT" != "command not found" ]; thenecho"$IMPACT"elseecho"Using fallback (direct callers only):"
claudemem --nologo callers SymbolName --raw
fi
Why This Matters:
v0.3.0 commands work for 90% of use cases (navigation, modification)
v0.4.0+ commands are specialized (code analysis, cleanup planning)
Scripts should work across versions with appropriate fallbacks
The Correct Workflow ⭐CRITICAL
Phase 1: Understand Structure First (ALWAYS DO THIS)
Before reading any code files, get the structural overview:
# For a specific task, get focused repo map
claudemem --nologo map "authentication flow" --raw
# Output shows relevant symbols ranked by importance (PageRank):# file: src/auth/AuthService.ts# line: 15-89# kind: class# name: AuthService# pagerank: 0.0921# signature: class AuthService# ---# file: src/middleware/auth.ts# ...
This tells you:
Which files contain relevant code
Which symbols are most important (high PageRank = heavily used)
The structure before you read actual code
Phase 2: Locate Specific Symbols
Once you know what to look for:
# Find exact location of a symbol
claudemem --nologo symbol AuthService --raw
# Output:# file: src/auth/AuthService.ts# line: 15-89# kind: class# name: AuthService# signature: class AuthService implements IAuthProvider# exported: true# pagerank: 0.0921# docstring: Handles user authentication and session management
Phase 3: Understand Dependencies
Before modifying code, understand what depends on it:
When to use: Architecture cleanup, tech debt assessment, before major refactoring
Empty Result Handling:
RESULT=$(claudemem --nologo dead-code --raw)
if [ -z "$RESULT" ] || [ "$RESULT" = "No dead code found" ]; thenecho"Codebase is clean - no dead code detected!"echo"This indicates good code hygiene."elseecho"$RESULT"fi
Static Analysis Limitations:
Dynamic imports (import()) may hide real callers
Reflection-based access not captured
External callers (other repos, CLI usage) not visible
Exported symbols excluded by default for this reason
claudemem test-gaps
Find high-importance code without test coverage.
# Find all test coverage gaps
claudemem --nologo test-gaps --raw
# Only critical gaps (high PageRank)
claudemem --nologo test-gaps --min-pagerank 0.05 --raw
Algorithm:
High PageRank (> 0.01 default) - Important code
Zero callers from test files (*.test.ts, *.spec.ts, *_test.go)
When to use: Test coverage analysis, QA planning, identifying critical gaps
Empty Result Handling:
RESULT=$(claudemem --nologo test-gaps --raw)
if [ -z "$RESULT" ] || [ "$RESULT" = "No test gaps found" ]; thenecho"Excellent! All high-importance code has test coverage."echo"Consider lowering --min-pagerank threshold for additional coverage."elseecho"$RESULT"fi
Static Analysis Limitations:
Test file detection based on naming patterns only
Integration tests calling code indirectly may not be detected
Mocked dependencies may show false positives
claudemem impact
Analyze the impact of changing a symbol using BFS traversal.
# Get all transitive callers
claudemem --nologo impact UserService --raw
# Limit depth for large codebases
claudemem --nologo impact UserService --max-depth 5 --raw
Algorithm:
BFS traversal from symbol to all transitive callers
When to use: Before ANY modification, refactoring planning, risk assessment
Empty Result Handling:
RESULT=$(claudemem --nologo impact FunctionName --raw)
if [ -z "$RESULT" ] || echo"$RESULT" | grep -q "No callers found"; thenecho"No callers found - this symbol appears unused or is an entry point."echo"If unused, consider running: claudemem --nologo dead-code --raw"echo"If entry point (API handler, main), this is expected."elseecho"$RESULT"fi
symbol:AuthService.authenticatefile:src/services/auth.tsline:45-89behavior:"Validates user credentials and generates JWT token"params:-name:credentialstype:LoginCredentialsdescription:"Email and password from login form"returns:type:AuthResultdescription:"JWT token and user profile on success, error on failure"side_effects:-"Updates user.lastLogin timestamp"-"Logs authentication attempt"-"May trigger rate limiting"
File Summary Fields
file:src/services/auth.tspurpose:"Core authentication service handling login, logout, and session management"exports:-AuthService(class)-authenticate(function)-validateToken(function)patterns:-"Dependency Injection (constructor takes IUserRepository)"-"Factory Pattern (createSession)"-"Strategy Pattern (IAuthProvider interface)"dependencies:-bcrypt(passwordhashing)-jsonwebtoken(JWTgeneration)-UserRepository(userdataaccess)
Using Document Types in Investigation
# Find function behavior without reading code
claudemem --nologo search "processPayment behavior" --use-case navigation --raw
# Output includes symbol_summary:# symbol: PaymentService.processPayment# behavior: "Charges customer card via Stripe and saves transaction"# side_effects: ["Updates balance", "Sends receipt email", "Logs to audit"]# Find file purposes for architecture understanding
claudemem --nologo search "file:services purpose" --use-case navigation --raw
# Find anti-patterns to avoid
claudemem --nologo search "anti_pattern SQL" --raw
Regenerating Enrichments
If codebase changes significantly:
# Re-index with LLM enrichment
claudemem index --enrich
# Or enrich specific files
claudemem enrich src/services/payment.ts
Workflow Templates
Standardized investigation patterns for common scenarios. All templates include error handling for empty results and version compatibility checks.
Template 1: Bug Investigation
Trigger: "Why is X broken?", "Find bug", "Root cause"
# Step 1: Locate the symptom
SYMBOL=$(claudemem --nologo symbol FunctionFromStackTrace --raw)
if [ -z "$SYMBOL" ]; thenecho"Symbol not found - check spelling or run: claudemem --nologo map 'related keywords' --raw"exit 1
fi# Step 2: Get full context (callers + callees)
claudemem --nologo context FunctionFromStackTrace --raw
# Step 3: Trace backwards to find root cause
claudemem --nologo callers suspectedSource --raw
# Step 4: Check full impact of the bug (v0.4.0+)
IMPACT=$(claudemem --nologo impact BuggyFunction --raw 2>/dev/null)
if [ -n "$IMPACT" ]; thenecho"$IMPACT"elseecho"Impact analysis requires claudemem v0.4.0+ or no callers found"echo"Fallback: claudemem --nologo callers BuggyFunction --raw"fi# Step 5: Read identified file:line ranges# Fix bug, verify callers still work# Step 6: Document impacted code for testing
Output Template:
## Bug Investigation Report**Symptom:** [Description]
**Root Cause:** [Location and explanation]
**Call Chain:** [How we got here]
**Impact Radius:** [What else is affected]
**Fix Applied:** [What was changed]
**Verification:** [Tests run, callers checked]
Claudemem uses static AST analysis. Some patterns are not captured:
Dynamic Imports
// NOT visible to static analysisconstmodule = awaitimport(`./modules/${name}`);
Result: May show as "dead code" but is actually used dynamically.
Action: Mark as "Potentially Dead - Manual Review"
External Callers
// Exported for external useexportfunctionpublicAPI() { ... }
Result: May show 0 callers but used by other repositories.
Action: Use --include-exported carefully, or mark as "Externally Called - Manual Review Required"
Reflection/Eval
// NOT visible to static analysisconst fn = obj[methodName]();
eval("functionName()");
Result: Callers not detected.
Action: Search codebase for eval, Object.keys, bracket notation.
Event-Driven Code
// NOT visible as direct callers
emitter.on('event', handler);
document.addEventListener('click', onClick);
Result:handler and onClick may show 0 callers.
Action: Check for event registration patterns.
Result:ServiceImpl may show 0 callers.
Action: Check DI container configuration.
Scenarios
Scenario 1: Bug Fix
Task: "Fix the null pointer exception in user authentication"
# Step 1: Get overview of auth-related code
claudemem --nologo map "authentication null pointer" --raw
# Step 2: Locate the specific symbol mentioned in error
claudemem --nologo symbol authenticate --raw
# Step 3: Check what calls it (to understand how it's used)
claudemem --nologo callers authenticate --raw
# Step 4: Read the actual code at the identified location# Now you know exactly which file:line to read
Scenario 2: Add New Feature
Task: "Add rate limiting to the API endpoints"
# Step 1: Understand API structure
claudemem --nologo map "API endpoints rate" --raw
# Step 2: Find the main API handler
claudemem --nologo symbol APIController --raw
# Step 3: See what the API controller depends on
claudemem --nologo callees APIController --raw
# Step 4: Check if rate limiting already exists somewhere
claudemem --nologo search "rate limit" --raw
# Step 5: Get full context for the modification point
claudemem --nologo context APIController --raw
Scenario 3: Refactoring
Task: "Rename DatabaseConnection to DatabasePool"
# Step 1: Find the symbol
claudemem --nologo symbol DatabaseConnection --raw
# Step 2: Find ALL callers (these all need updating)
claudemem --nologo callers DatabaseConnection --raw
# Step 3: The output shows every file:line that references it# Update each location systematically
Scenario 4: Understanding Unfamiliar Codebase
Task: "How does the indexing pipeline work?"
# Step 1: Get high-level structure
claudemem --nologo map "indexing pipeline" --raw
# Step 2: Find the main entry point (highest PageRank)
claudemem --nologo symbol Indexer --raw
# Step 3: Trace the flow - what does Indexer call?
claudemem --nologo callees Indexer --raw
# Step 4: For each major callee, get its callees
claudemem --nologo callees VectorStore --raw
claudemem --nologo callees FileTracker --raw
# Now you have the full pipeline traced
Token Efficiency Guide
Action
Token Cost
When to Use
map (focused)
~500
Always first - understand structure
symbol
~50
When you know the name
callers
~100-500
Before modifying anything
callees
~100-500
To understand dependencies
context
~200-800
For complex modifications
search
~1000-3000
When you need actual code
search --map
~1500-4000
For unfamiliar codebases
Optimal order: map → symbol → callers/callees → search (only if needed)
This pattern typically uses 80% fewer tokens than blind exploration.
Integration Pattern for Agents
For maximum efficiency, follow this pattern:
1. RECEIVE TASK
↓
2. claudemem --nologo map "<task keywords>" --raw
→ Understand structure, identify key symbols
↓
3. claudemem --nologo symbol <high-pagerank-symbol> --raw
→ Get exact location
↓
4. claudemem --nologo callers <symbol> --raw (if modifying)
→ Know the impact radius
↓
5. claudemem --nologo callees <symbol> --raw (if needed)
→ Understand dependencies
↓
6. READ specific file:line ranges (not whole files)
↓
7. MAKE CHANGES with full awareness
↓
8. CHECK callers still work
PageRank: Understanding Symbol Importance
PageRank measures how "central" a symbol is in the codebase:
PageRank
Meaning
Action
> 0.05
Core abstraction
Understand this first - everything depends on it
0.01-0.05
Important symbol
Key functionality, worth understanding
0.001-0.01
Standard symbol
Normal code, read as needed
< 0.001
Utility/leaf
Helper functions, read only if directly relevant
Why PageRank matters:
High-PageRank symbols are heavily used → understand them first
Low-PageRank symbols are utilities → read later if needed
Focus on high-PageRank symbols to understand architecture quickly
🔴 ANTI-PATTERNS (DO NOT DO THESE)
╔══════════════════════════════════════════════════════════════════════════════╗
║ COMMON MISTAKES TO AVOID ║
╠══════════════════════════════════════════════════════════════════════════════╣
║ ║
║ ❌ Anti-Pattern 1: Blind File Reading ║
║ → BAD: cat src/core/*.ts | head -1000 ║
║ → GOOD: claudemem --nologo map "your task" --raw ║
║ → WHY: Wastes tokens on irrelevant code, misses important files ║
║ ║
║ ❌ Anti-Pattern 2: Grep Without Context ║
║ → BAD: grep -r "Database" src/ ║
║ → GOOD: claudemem --nologo symbol Database --raw ║
║ → WHY: Grep returns string matches, not semantic relationships ║
║ ║
║ ❌ Anti-Pattern 3: Modifying Without Impact Analysis ║
║ → BAD: Edit src/auth/tokens.ts without knowing callers ║
║ → GOOD: claudemem --nologo callers generateToken --raw FIRST ║
║ → WHY: Changes may break callers you don't know about ║
║ ║
║ ❌ Anti-Pattern 4: Searching Before Mapping ║
║ → BAD: claudemem search "fix the bug" --raw ║
║ → GOOD: claudemem --nologo map "feature" --raw THEN search ║
║ → WHY: Search results lack context without structural understanding ║
║ ║
║ ❌ Anti-Pattern 5: Ignoring PageRank ║
║ → BAD: Read every file that matches "Database" ║
║ → GOOD: Focus on high-PageRank symbols first ║
║ → WHY: Low-PageRank = utilities, High-PageRank = core abstractions ║
║ ║
║ ❌ Anti-Pattern 6: Not Using --nologo ║
║ → BAD: claudemem search "query" (includes ASCII art) ║
║ → GOOD: claudemem --nologo search "query" --raw ║
║ → WHY: Logo and decorations make parsing unreliable ║
║ ║
╚══════════════════════════════════════════════════════════════════════════════╝
# Index current project
claudemem index
# Check status
claudemem --version && ls -la .claudemem/index.db 2>/dev/null
Framework Documentation (v0.7.0+) ⭐NEW
Claudemem v0.7.0+ includes automatic framework documentation fetching for your project dependencies. Documentation is indexed alongside your code, enabling unified semantic search across both.
Quick Reference
# Core documentation commands
claudemem docs status # Show indexed libraries and cache state
claudemem docs fetch # Fetch docs for all detected dependencies
claudemem docs fetch react vue # Fetch specific libraries
claudemem docs providers # List available documentation providers
claudemem docs refresh # Force refresh all cached documentation
claudemem docs clear # Clear all documentation cache
claudemem docs clear react # Clear specific library cache
Documentation Providers
Claudemem uses a provider hierarchy with automatic fallback:
# Option 1: Run init (includes docs configuration)
claudemem init
# Option 2: Configure Context7 manually (optional, for best coverage)export CONTEXT7_API_KEY=your_key
# Get free API key at: https://context7.com/dashboard
Usage Examples
# Check current documentation status
claudemem docs status
# Output:# 📚 Documentation Status## Enabled: Yes# Providers: Context7, llms.txt, DevDocs# Libraries: 12 indexed# Cache Age: 2h 15m## Indexed Libraries:# react (v18) via Context7 - 145 chunks# typescript (v5) via Context7 - 89 chunks# express (v4) via llms.txt - 34 chunks# ...# Fetch documentation for all project dependencies
claudemem docs fetch
# Output:# 📚 Fetching Documentation## [1/8] react... ✓ 145 chunks via Context7# [2/8] typescript... ✓ 89 chunks via Context7# [3/8] express... ✓ 34 chunks via llms.txt# [4/8] lodash... ✓ 67 chunks via DevDocs# ...# Fetch specific library
claudemem docs fetch fastapi
# View available providers
claudemem docs providers
# Force refresh (clears cache, refetches)
claudemem docs refresh
Unified Search (Code + Documentation)
After indexing documentation, claudemem search returns results from both your codebase and framework documentation:
claudemem --nologo search "how to use React hooks" --raw
# Output includes:# --- Your Code ---# file: src/components/UserProfile.tsx# line: 12-45# kind: function# name: useUserProfile# score: 0.89# content: Custom hook for user profile management...# ---# --- React Documentation ---# library: react# section: Hooks Reference# title: useEffect# score: 0.87# content: The useEffect Hook lets you perform side effects...# ---# library: react# section: Hooks Reference# title: useState# score: 0.85# content: useState is a Hook that lets you add state...
When to Use Documentation Commands
Scenario
Command
Why
New project setup
claudemem docs fetch
Index docs for all dependencies
Learning new library
claudemem docs fetch <library>
Get searchable reference
Updated dependencies
claudemem docs refresh
Refresh to get new versions
Check what's indexed
claudemem docs status
View cache state
Clear space
claudemem docs clear
Remove cached documentation
Integration with Investigation Workflow
Add documentation fetch to your investigation workflow:
# ENHANCED Investigation Workflow (v0.7.0+)# Step 0: Ensure framework docs are available (one-time)
claudemem docs status || claudemem docs fetch
# Step 1: Map architecture (now includes library patterns)
claudemem --nologo map "authentication" --raw
# Step 2: Search both code AND framework docs
claudemem --nologo search "JWT token validation" --raw
# Returns: your auth code + library docs on JWT handling# Step 3: Understand how the library recommends usage
claudemem --nologo search "react best practices hooks" --raw
# Returns: your patterns + React official guidance
Version Information
The claudemem docs command requires v0.7.0+. Check your version:
claudemem --version
# Expected: 0.7.0 or higher
Note: If claudemem docs help returns "Unknown command", upgrade your claudemem installation.
Index Freshness Check (v0.5.0)
Before proceeding with investigation, verify the index is current:
# Count files modified since last index
STALE_COUNT=$(find . -type f \( -name "*.ts" -o -name "*.tsx" -o -name "*.js" -o -name "*.jsx" -o -name "*.py" -o -name "*.go" -o -name "*.rs" \) \
-newer .claudemem/index.db 2>/dev/null | grep -v "node_modules" | grep -v ".git" | grep -v "dist" | grep -v "build" | wc -l)
STALE_COUNT=$((STALE_COUNT + 0)) # Normalize to integerif [ "$STALE_COUNT" -gt 0 ]; then# Get index time with explicit platform detectionif [[ "$OSTYPE" == "darwin"* ]]; then
INDEX_TIME=$(stat -f "%Sm" -t "%Y-%m-%d %H:%M" .claudemem/index.db 2>/dev/null)
else
INDEX_TIME=$(stat -c "%y" .claudemem/index.db 2>/dev/null | cut -d'.' -f1)
fi
INDEX_TIME=${INDEX_TIME:-"unknown time"}# Use AskUserQuestion to ask user how to proceed# Options: [1] Reindex now (Recommended), [2] Proceed with stale index, [3] Cancelfi
AskUserQuestion Template:
AskUserQuestion({
questions: [{
question: `${STALE_COUNT} files have been modified since the last index (${INDEX_TIME}). The claudemem index may be outdated, which could cause missing or incorrect results. How would you like to proceed?`,
header: "Index Freshness Warning",
multiSelect: false,
options: [
{
label: "Reindex now (Recommended)",
description: "Run claudemem index to update. Takes ~1-2 minutes."
},
{
label: "Proceed with stale index",
description: "Continue investigation. May miss recent code changes."
},
{
label: "Cancel investigation",
description: "I'll handle this manually."
}
]
}]
})
Result Validation Guidelines
After Every Command
Check exit code - Non-zero indicates failure
Check for empty results - May need reindex or different query
Validate relevance - Results should match query semantics
Validation Examples
# map validation
RESULTS=$(claudemem --nologo map "authentication" --raw)
EXIT_CODE=$?
if [ "$EXIT_CODE" -ne 0 ]; thenecho"ERROR: claudemem command failed"# Diagnose index health
DIAGNOSIS=$(claudemem --version && ls -la .claudemem/index.db 2>&1)
# Use AskUserQuestionfiif [ -z "$RESULTS" ]; thenecho"WARNING: No results found - may need reindex or different query"# Use AskUserQuestionfiif ! echo"$RESULTS" | grep -qi "auth\|login\|user\|session"; thenecho"WARNING: Results may not be relevant to authentication query"# Use AskUserQuestionfi# symbol validation
RESULTS=$(claudemem --nologo symbol UserService --raw)
if ! echo"$RESULTS" | grep -q "name: UserService"; thenecho"WARNING: UserService not found - check spelling or reindex"# Use AskUserQuestionfi# search validation
RESULTS=$(claudemem --nologo search "error handling" --raw)
MATCH_COUNT=0
for kw in error handling catch try; doifecho"$RESULTS" | grep -qi "$kw"; then
MATCH_COUNT=$((MATCH_COUNT + 1))
fidoneif [ "$MATCH_COUNT" -lt 2 ]; thenecho"WARNING: Results may not be relevant to error handling query"# Use AskUserQuestionfi
FALLBACK PROTOCOL
CRITICAL: Never use grep/find/Glob without explicit user approval.
If claudemem fails or returns irrelevant results:
STOP - Do not silently switch to grep/find
DIAGNOSE - Run claudemem status to check index health
COMMUNICATE - Tell user what happened
ASK - Get explicit user permission via AskUserQuestion
// Fallback AskUserQuestion TemplatesAskUserQuestion({
questions: [{
question: "claudemem [command] failed or returned no relevant results. How should I proceed?",
header: "Investigation Issue",
multiSelect: false,
options: [
{ label: "Reindex codebase", description: "Run claudemem index (~1-2 min)" },
{ label: "Try different query", description: "Rephrase the search" },
{ label: "Use grep (not recommended)", description: "Traditional search - loses semantic understanding" },
{ label: "Cancel", description: "Stop investigation" }
]
}]
})
Grep Fallback Warning:
If user explicitly chooses grep fallback, display this warning:
## WARNING: Using Fallback Search (grep)
You have chosen to use grep as a fallback. Please understand the limitations:
| Feature | claudemem | grep |
|---------|-----------|------|
| Semantic understanding | Yes | No |
| Call graph analysis | Yes | No |
| Symbol relationships | Yes | No |
| PageRank ranking | Yes | No |
| False positives | Low | High |
**Recommendation:** After completing this task, run `claudemem index` to rebuild
the index for future investigations.
Proceeding with grep...
See ultrathink-detective skill for complete Fallback Protocol documentation.
Quality Checklist
Before completing a claudemem workflow, ensure:
claudemem CLI is installed (v0.3.0+)
Codebase is indexed (check with claudemem status)
Checked index freshness before starting ⭐NEW in v0.5.0
Started with map to understand structure ⭐CRITICAL
Used --nologo --raw for all commands
Validated results after every command ⭐NEW in v0.5.0
Checked callers before modifying any symbol
Focused on high-PageRank symbols first
Read only specific file:line ranges (not whole files)
