cm-deep-search

Detect oversized projects and propose local semantic search via qmd.

48|23|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/tody-agent/codymaster --skill cm-deep-search
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cm-deep-search
Source: https://github.com/tody-agent/codymaster/tree/main/skills/cm-deep-search
Command: npx skills add https://github.com/tody-agent/codymaster --skill cm-deep-search

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Optional power-up — detects oversized codebases/docs and suggests tobi/qmd for local semantic search. Bridges cm-continuity (working memory) with long-term document retrieval. Zero-config detection, non-intrusive suggestion.

Core Features & Use Cases

  • Non-intrusive prompts that suggest qmd when thresholds are met
  • Seamless bridging of in-session memory with long-term document search
  • Quick install and integration guide for qmd to enable semantic search across docs and source

Quick Start

Install qmd globally, index your docs and source code, and run embed to enable semantic search.

Frequently Asked Questions about cm-deep-search

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

FAQPage Schema
How do I set up semantic search for a large codebase and documentation?

To set up semantic search for a large codebase, install qmd globally, index your source code and documentation, and run embed. This enables local semantic retrieval across your project files.

How does semantic search handle oversized project documentation?

Semantic search handles oversized project documentation by applying non-intrusive prompts during planning phases. It detects size thresholds and bridges in-session working memory with long-term document retrieval.

Do I need to configure anything to detect when a project needs local semantic search?

No configuration is needed to detect when a project needs local semantic search. The detection runs automatically during project scans and documentation reviews, providing non-intrusive suggestions when size thresholds are crossed.

What is the best way to integrate in-session memory with long-term codebase retrieval?

The best way to integrate in-session memory with long-term codebase retrieval is by bridging working memory with local document search. This is achieved by installing qmd to index and embed your documentation and source code.

When should I avoid using local semantic search for my documentation?

You should avoid using local semantic search when your project does not cross defined size thresholds. It is specifically designed as an optional power-up for oversized codebases and documentation, rather than smaller projects.