rlm-search

Search codebases using summary scan, vector search, and exact grep phases.

5|3|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/richfrem/agent-plugins-skills --skill rlm-search
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rlm-search
Source: https://github.com/richfrem/agent-plugins-skills/tree/main/plugins/rlm-factory/skills/rlm-search
Command: npx skills add https://github.com/richfrem/agent-plugins-skills --skill rlm-search

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Locating relevant code, documentation, and architecture context in large repositories is slow and error-prone. This skill enforces a deterministic three-phase search workflow that starts with a lightweight summary, proceeds to a semantically informed vector search, and ends with a precise grep/exact-match pass, dramatically reducing toil and missed context.

Core Features & Use Cases

  • Three-phase search pipeline: Phase 1 performs a rapid RLM Summary Scan, Phase 2 retrieves semantically relevant chunks via vector search, Phase 3 narrows to exact matches with targeted grep.
  • Scoped, reproducible results: Always works in a bounded, auditable sequence to prevent missed context and ensure repeatable results across large codebases.
  • Use Case: When locating architecture docs or the implementation details of a function across a sprawling project, use this skill to surface the most relevant material quickly and with high precision.

Quick Start

Invoke the rlm-search to locate architecture or code references by starting with a summary scan, followed by vector search, and finishing with a scoped exact match.

Frequently Asked Questions about rlm-search

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

FAQPage Schema
What is the best way to search for code and architecture context in a large repository?

The best way to search a large repository is using a three-phase workflow: starting with a quick summary scan, proceeding to semantic vector search, and finishing with exact grep. This scoped sequence prevents missed context and ensures precise results.

How do I use vector search and grep together for code discovery?

You use vector search and grep together by applying a sequential pipeline where vector search first retrieves semantically relevant chunks, followed by a targeted grep pass to narrow down to exact matches, yielding highly precise code discovery results.

Why does my semantic code search miss exact implementation details?

Semantic code search often misses exact implementation details because it lacks a precise matching pass. Adding a final phase with targeted grep after the vector search ensures you capture exact string matches without missing critical context.

How do I locate architecture documentation efficiently across a sprawling project?

To locate architecture documentation efficiently across a sprawling project, execute a rapid summary scan first, then use vector search for semantic retrieval, and finally apply scoped exact matching to surface the most relevant material quickly.

Can I skip the summary scan and go straight to exact grep when searching code?

No, you cannot skip the summary scan. The three-phase search workflow enforces a non-skippable sequence starting with a summary scan, moving to vector search, and ending with grep to guarantee reproducible, auditable results across large codebases.