repo-scout

Scan a codebase to identify existing patterns, conventions, and reusable components.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fast repository scouting to discover existing patterns, conventions, and related code paths that should guide implementation.

Core Features & Use Cases

  • Pattern discovery: identify naming conventions, file layouts, and module boundaries to align with project standards.
  • Conventions surface: surface reusable components, utilities, and anti-patterns to inform reuse and avoid duplication.
  • Use case guidance: provide insights on where patterns apply during planning and development in real-world repos.

Quick Start

Run the repo-scout tool to scan the repository for patterns and conventions.

Frequently Asked Questions about repo-scout

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

FAQPage Schema
How do I discover existing codebase conventions and patterns before writing new code?

To discover codebase conventions, scan the repository structure to identify naming conventions, file layouts, and module boundaries. This surfaces existing patterns and reusable components, ensuring new code aligns with project standards and avoids duplication.

What is the best way to find reusable components and utilities across multiple directories?

Finding reusable components across multiple directories involves scanning the codebase to surface existing utilities and related code paths. This approach identifies available modules and anti-patterns, informing reuse decisions and preventing code duplication during implementation.

How do I scan a repository to locate related code paths for a new feature implementation?

Scanning a repository to locate related code paths requires exploring the project structure across multiple languages and directories. The process identifies existing conventions and related code, providing insights that guide planning and development for real-world implementation.

Does this pattern discovery approach work for repositories with multiple programming languages?

Yes, pattern discovery works for repositories with multiple programming languages. The tool scans across multiple languages and directories to surface conventions, locate reusable components, and identify module boundaries, ensuring consistent project norms regardless of language diversity.

When do I need to scout a repository for conventions and anti-patterns?

Scouting a repository for conventions and anti-patterns is needed before planning a new feature or refactoring existing code. Identifying project norms, reusable utilities, and anti-patterns early informs implementation strategy and ensures alignment with established standards.

Can I use codebase scanning to identify module boundaries and file layout standards?

Yes, codebase scanning identifies module boundaries and file layout standards by analyzing the repository structure. This process surfaces naming conventions and structural patterns, providing clear guidance on where new modules should be placed and how they should be organized.