docs-search

Search and synthesize project documentation into cited answers.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/real-case/marvin-toolkit --skill docs-search-real-case
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: docs-search
Source: https://github.com/real-case/marvin-toolkit/tree/main/plugins/marvin/skills/docs-search
Command: npx skills add https://github.com/real-case/marvin-toolkit --skill docs-search-real-case

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers waste time hunting through READMEs, ADRs, API specs, and scattered markdown files when they need to understand how a project works. This Skill searches broadly across the codebase and documentation, then synthesizes a direct answer with file-and-line citations instead of dumping a list of file paths. ## Core Features & Use Cases - Documentation landscape discovery: Scans for README, CHANGELOG, docs/ directories, ADRs, OpenAPI specs, and config files to map what documentation exists before searching. - Multi-strategy search: Combines content grep, filename globbing, code inspection (docstrings, tests, route definitions), and git history checks to find answers even when prose docs are missing or stale. - Synthesized answers with citations: Leads with the answer, cites sources as file:line references, and flags conflicts, gaps, and stale documentation. - Use Case: A new team member asks "how does authentication work here?" The Skill scans docs and code, reads the auth module and its tests, and returns an explanation citing src/auth/README.md:15-28 while warning that the README contradicts the current middleware behavior. ## Quick Start Ask where a feature is documented or how a specific part of the project works, and receive a synthesized answer with source citations.

Frequently Asked Questions about docs-search

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

FAQPage Schema
How do I find where a feature is documented in a repo?▼

Search broadly with grep for the concept name and its synonyms across markdown files and code comments, then glob for files named after the feature. Read the most relevant matches and cite answers with file paths and line numbers.

How to answer questions about project architecture from docs?▼

Start by mapping the documentation landscape: README, ARCHITECTURE.md, docs/ directories, and ADRs. Then combine content search with reading source code, type definitions, and tests, since code often documents behavior more accurately than prose.

What should I do when documentation contradicts the code?▼

Surface both sources and note the discrepancy explicitly rather than picking one silently. The code is usually the source of truth, and git log on the doc file reveals whether it has gone stale relative to recent code changes.

Can documentation search work when docs are missing or outdated?▼

Yes. When prose docs are absent, treat docstrings, test assertions, route definitions, and well-named functions as documentation. State clearly what is undocumented, suggest where the missing docs should live, and offer to draft them.

How do I check if project documentation is stale?▼

Run git log on the documentation file and compare its last update against recent changes to the related code. If the doc has not been touched in months while the code changed recently, flag it as potentially outdated instead of presenting it as authoritative.