code-search-selector

Apply semantic search before reading files during codebase audits.

278|29|Updated Nov 4, 2025
One-click install
npx skills add https://github.com/MadAppGang/claude-code --skill code-search-selector-madappgang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-search-selector
Source: https://github.com/MadAppGang/claude-code/tree/main/plugins/code-analysis/skills/code-search-selector
Command: npx skills add https://github.com/MadAppGang/claude-code --skill code-search-selector-madappgang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill auto-invokes semantic search when user asks for audit/investigate/map the codebase, preventing tool familiarity bias toward Read/Glob.

Core Features & Use Cases

  • Mandatory gate before reading 3+ files
  • Decision tree to classify semantic vs exact matches
  • Step-by-step workflow for semantic discovery

Quick Start

If the user asks to "map the codebase," run claudemem search instead of bulk reads.

Frequently Asked Questions about code-search-selector

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

FAQPage Schema
How do I search code semantically before reading multiple files during audits?

Semantic search gates file reads by understanding intent before bulk access. This Skill auto-invokes semantic search when you ask to audit or map a codebase, preventing inefficient direct reads across large repositories and ensuring keyword-triggered discovery identifies implementations across the entire codebase first.

When should I use semantic search instead of direct file reads for code investigation?

Use semantic search when investigating, auditing, or mapping codebases to understand architecture and trace integration points. This Skill applies semantic-first logic before reading 3+ files, classifying whether your query needs semantic matching or exact keyword lookup to avoid tool bias toward bulk reads.

Can I automatically gate codebase searches before reading files?

Yes. This Skill enforces mandatory pre-read semantic gating through a decision tree that classifies queries and orchestrates predefined tools—Bash, Read, and question prompts—to deliver semantic results first, satisfying requirements for keyword-triggered auto-invocation during comprehensive repository investigation.

What's the best way to map a large codebase efficiently?

Map large codebases using semantic search before direct reads to avoid inefficiency. This Skill performs step-by-step semantic discovery when you ask to map or audit, automatically classifying your intent and orchestrating workflow tools to identify implementations and integration points comprehensively without unnecessary file access.

How do I trace integration points across a large repository?

Semantic search traces integration points by understanding functional requirements before reading files. This Skill gates comprehensive identification across large repositories through predefined orchestration, ensuring you discover relevant implementations through semantic-first results rather than manual bulk exploration.