retriever

Search codebase, logs, and configurations with Grep, Glob, and Read tools.

1|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/jimmymalhan/codereview-pilot --skill retriever
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retriever
Source: https://github.com/jimmymalhan/codereview-pilot/tree/main/.claude/skills/retriever
Command: npx skills add https://github.com/jimmymalhan/codereview-pilot --skill retriever

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of finding and validating evidence within a codebase or logs, ensuring that claims made during incident diagnosis are backed by verifiable data.

Core Features & Use Cases

  • Evidence Gathering: Searches code files, logs, and configurations using Grep, Glob, and Read tools.
  • Citation Validation: Ensures that all gathered evidence is linked to actual file paths and line numbers.
  • Use Case: When diagnosing a performance issue, this Skill can pinpoint the exact lines of code or log entries responsible by searching the repository and validating each finding.

Quick Start

Use the retriever skill to find all occurrences of the function 'calculate_total' within the codebase.

Frequently Asked Questions about retriever

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

FAQPage Schema
How do I gather evidence for incident diagnosis with file and line citations?

Evidence gathering for incident diagnosis is automated by searching codebases, logs, and configurations using Grep, Glob, and Read tools, ensuring all findings are validated with specific file:line citations.

How do I search a codebase and validate findings for code review?

Codebase search for code review is performed by applying Grep, Glob, and Read tools across files, validating every discovered occurrence with precise file path and line number citations.

Do I need MCP integration to search logs and configurations for incident diagnosis?

MCP integration is required for repository access to enable searching logs and configurations, applying strict citation validation protocols to ensure all incident diagnosis findings are verifiable.

What's the best way to validate codebase search results during incident diagnosis?

Validating codebase search results during incident diagnosis is best handled by a multi-phase agentic approach that enforces strict citation validation, linking every claim to exact file paths and line numbers.

Why do my incident diagnosis findings lack verifiable evidence from logs and code?

Incident diagnosis findings often lack verifiable evidence because claims are not linked to actual data, a problem solved by enforcing strict citation validation protocols with file:line references during searches.

Can I search for all occurrences of a specific function across the codebase?

Searching for all occurrences of a specific function across the codebase is supported by applying Grep, Glob, and Read tools to locate and validate every instance with file:line citations.