name	Repo Map
description	Map repository structure, ownership boundaries, and relevant files.
when-to-use	Use when a task requires understanding the current codebase.
user-invocable	false
context	inline

Inspect the repository with fast file search and targeted reads. Return:

High-level modules and entry points.
Files most relevant to the current task.
Existing patterns to reuse.
Unknowns that need direct code reading.
Detected stack, package/build/test manifests, generated-code boundaries, and important conventions.
Ownership boundaries: client, server, data, integration, infra, tests, docs, and scripts where applicable.
Risky areas: global state, migrations, public APIs, permission checks, async jobs, deployment config, or compatibility layers.

Include paths and short evidence, not guesses.

Más de este repositorio

mismo repositorio

Convert source notes into claim-level evidence with confidence and limitations.

Verify source traceability, artifact completeness, and citation correctness before citation_qa gate.

Write an evidence-backed final research report from sources and the evidence matrix.

Review research method quality, source diversity, bias, and conclusion strength.

Convert a broad research request into subquestions, assumptions, and source criteria.

Design and execute a multi-round SearxNG/arXiv search strategy.

name	Repo Map
description	Map repository structure, ownership boundaries, and relevant files.
when-to-use	Use when a task requires understanding the current codebase.
user-invocable	false
context	inline

Inspect the repository with fast file search and targeted reads. Return:

High-level modules and entry points.
Files most relevant to the current task.
Existing patterns to reuse.
Unknowns that need direct code reading.
Detected stack, package/build/test manifests, generated-code boundaries, and important conventions.
Ownership boundaries: client, server, data, integration, infra, tests, docs, and scripts where applicable.
Risky areas: global state, migrations, public APIs, permission checks, async jobs, deployment config, or compatibility layers.

Include paths and short evidence, not guesses.