repo-search

Search and map codebases for files, symbols, and patterns.

4|2|Updated Aug 27, 2025
One-click install
npx skills add https://github.com/finger-gun/sisu --skill repo-search
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-search
Source: https://github.com/finger-gun/sisu/tree/main/packages/skills/skill-repo-search
Command: npx skills add https://github.com/finger-gun/sisu --skill repo-search

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers quickly locate files, symbols, and patterns across a codebase, reducing manual search time and improving discovery accuracy.

Core Features & Use Cases

  • Identify keywords, file patterns, or APIs to locate
  • Use file globbing or listing to narrow scope
  • Use content search to find key matches
  • Read files around matches for context
  • Summarize findings and next steps
  • See resources/search-cheatsheet.md for guidance and templates.

Quick Start

Point the skill at a codebase to identify keywords, files, and APIs, then summarize findings and next steps.

Frequently Asked Questions about repo-search

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

FAQPage Schema
How do I search for specific code patterns and symbols across a large codebase?

To search for specific patterns across a codebase, use file globbing to narrow the scope, then apply content search to locate key matches. Read surrounding files for context and summarize findings to map symbols and APIs efficiently.

What is the best way to discover files and APIs in a monorepo?

The best way to discover files and APIs in a monorepo is to identify target keywords and file patterns, use content search to find matches, and read nearby files for context. This approach reduces manual search time and improves discovery accuracy.

Can I audit a codebase by searching for specific keywords and listing matching files?

Yes, you can audit a codebase by identifying keywords, file patterns, or APIs to locate. Use file listing and content search to find matches, then read the files around those matches to gather context for auditing and documentation alignment.

How do I get context around matches when searching for symbols in a repository?

To get context around matches when searching for symbols, first locate the matches using content search within a narrowed file scope. Then, read the files around those matches to understand the surrounding code and summarize the findings for next steps.

Does codebase discovery work without specifying file patterns upfront?

Codebase discovery can work without strict file patterns by listing files to narrow scope, though specifying file patterns or globbing upfront improves search accuracy. Identifying target keywords and APIs first helps guide the overall content search.