context-scout

Explore large codebases using RepoPrompt codemaps and slices.

Updated Jan 22, 2026
One-click install
npx skills add https://github.com/raydocs/antiflowskills --skill context-scout
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-scout
Source: https://github.com/raydocs/antiflowskills/tree/main/.factory/skills/context-scout
Command: npx skills add https://github.com/raydocs/antiflowskills --skill context-scout

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Token-efficient codebase exploration using RepoPrompt codemaps and slices. Use when you need deep codebase understanding without bloating context, finding all pieces of a feature across many files, or building context for code review. Requires rp-cli on macOS; degrades to repo-scout otherwise.

Core Features & Use Cases

  • Token-efficient exploration across large codebases using codemaps and slices.
  • Find all pieces of a feature across multiple files and understand architecture quickly.
  • Build context for code reviews when rp-cli is unavailable, gracefully degrading to repo-scout.

Quick Start

Start by verifying rp-cli availability and initiating a deep codebase exploration to gather context for a feature.

Frequently Asked Questions about context-scout

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

FAQPage Schema
How do I explore a large codebase to understand architecture without exceeding token limits?

Token-efficient codebase exploration uses codemaps and slices to understand large features across many files without bloating context. This approach allows you to perform deep-dive reviews and architecture discovery while managing token usage effectively.

How do I find all pieces of a feature scattered across multiple files for a code review?

You can find all pieces of a feature across multiple files by using token-efficient codebase exploration to gather the necessary context. This method enables quick architecture discovery and builds the precise context needed for thorough code reviews.

Do I need rp-cli installed to perform token-efficient codebase exploration?

Token-efficient codebase exploration requires rp-cli on macOS to function optimally. However, if rp-cli is unavailable, the process gracefully degrades to use repo-scout, ensuring you can still explore unfamiliar repositories.

What is the best way to onboard into unfamiliar repositories without consuming too many tokens?

The best way to onboard in unfamiliar repositories is using token-efficient codebase exploration with codemaps and slices. This technique quickly reveals the underlying architecture and feature distribution across files while strictly managing context window consumption.

Can I use this codebase exploration method if rp-cli is unavailable on my system?

Yes, you can still perform codebase exploration if rp-cli is unavailable, because the system gracefully degrades to repo-scout. This fallback mechanism ensures you can continue building context for code reviews and architecture discovery without interruption.

Why does my codebase context bloat when I try to review a large feature across many files?

Context bloats during large feature reviews because standard exploration loads entire files into the context window. Using token-efficient codebase exploration with codemaps and slices mitigates this by extracting only the necessary architectural context across multiple files.