mgrep-code-search

Index codebases with a watcher and search them using natural language queries.

321|26|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/mkurman/tamux --skill mgrep-code-search-mkurman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mgrep-code-search
Source: https://github.com/mkurman/tamux/tree/main/skills/productivity/agent-skills/mgrep-code-search
Command: npx skills add https://github.com/mkurman/tamux --skill mgrep-code-search-mkurman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Semantic code search across large codebases helps developers quickly locate where features are implemented and understand intent without manual inspection.

Core Features & Use Cases

  • Semantic search across codebases: natural language queries yield relevant code.
  • Watcher/indexing workflow: indexes repositories while respecting .gitignore and hidden files, keeping results current.
  • Use Case: quickly identify where a feature is implemented across a nested directory structure.

Quick Start

Index the codebase with the watcher and perform a semantic search using natural language queries.

Frequently Asked Questions about mgrep-code-search

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

FAQPage Schema
What is semantic code search and how does it differ from grep?

Semantic code search uses natural language queries to locate implementations and understand intent, returning precise file references and context. Unlike traditional grep, it captures relationships between components in large or nested repositories where context is missed.

How do I search a large codebase to find where a feature is implemented?

To search a large codebase semantically, index the repository files using a watcher that respects .gitignore, then query the index with natural language to quickly identify relevant code and file references across nested directory structures.

Does semantic code search work with nested repositories and hidden files?

Semantic code search supports large or nested repositories by indexing files through a watcher workflow. The watcher respects .gitignore rules and hidden files, keeping the searchable index current and accurate for natural language queries.

Can I use natural language queries to understand code intent across a codebase?

Yes, you can use natural language queries to semantically search a codebase and understand implementation intent. The search tool queries a maintained index to return precise file references and relevant context without requiring manual inspection.

What's the best way to locate code in a large repository without manual inspection?

The best way to locate code without manual inspection is using semantic code search. It requires a watcher to index the repository files and a semantic search tool to query the index, yielding relevant code and context from natural language inputs.

Why does traditional grep miss context when searching codebases?

Traditional grep misses context because it relies on exact string matching without understanding structure or relationships between components. Semantic code search overcomes this by indexing file context and intent for natural language retrieval.