rls-query

Query codebase patterns, conventions, and file locations via librarian and explorer components.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/j-mckerracher/agent-research --skill rls-query
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rls-query
Source: https://github.com/j-mckerracher/agent-research/tree/main/.claude/skills/rls-query
Command: npx skills add https://github.com/j-mckerracher/agent-research --skill rls-query

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Query the Reference Librarian and Information Explorer to retrieve codebase knowledge, patterns, conventions, and file locations when you need authoritative guidance without scanning the entire repository.

Core Features & Use Cases

  • Orchestrates knowledge queries across the codebase by coordinating librarian and explorer components.
  • Returns structured, actionable insights including locations, patterns, and conventions for design decisions.
  • Use Case: quickly locate where a feature is implemented and what conventions apply, then plan implementation.

Quick Start

Ask the broker a knowledge question about the codebase to locate implementations, patterns, or conventions.

Frequently Asked Questions about rls-query

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

FAQPage Schema
How do I find where a feature is implemented in a codebase without scanning the entire repository?

To find codebase patterns and file locations, query the coordinated librarian and explorer components. They orchestrate knowledge retrieval across the repository to locate implementations, conventions, and standards, then synthesize the results into a compact JSON answer.

What is the best way to retrieve codebase conventions and design standards for a new feature?

To retrieve codebase conventions, query the librarian and explorer components to extract authoritative design standards and patterns. This returns structured insights covering locations and conventions to guide implementation planning decisions.

Can I get structured JSON output when querying for codebase patterns and file locations?

Yes, querying codebase patterns returns a compact JSON answer. The broker orchestrates librarian queries, optional exploration, and synthesis to deliver structured file locations and conventions in JSON format.

Does this codebase knowledge query approach work for understanding existing standards before planning an implementation?

Yes, querying the librarian retrieves authoritative conventions and codebase patterns to guide implementation planning. It locates existing implementations and standards to inform development decisions before you write code.

When should I not use a coordinated librarian and explorer query for codebase knowledge?

Avoid coordinated librarian and explorer queries for simple string matching tasks. This approach targets complex codebase knowledge synthesis involving patterns, conventions, and file locations rather than basic text search operations.