finding-files

Locate codebase files using naming, content, dependency, and configuration patterns.

8|1|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/bostonaholic/team --skill finding-files
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finding-files
Source: https://github.com/bostonaholic/team/tree/main/skills/finding-files
Command: npx skills add https://github.com/bostonaholic/team --skill finding-files

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the challenge of locating specific, relevant files within large or complex codebases by applying a structured, multi-layered search strategy.

Core Features & Use Cases

  • Multi-Strategy Search: Employs globbing, content grepping, dependency tracing, and directory exploration to ensure no relevant file is overlooked.
  • Multi-Repo Support: Automatically scales search operations across multiple repositories when defined in the project scope.
  • Use Case: When investigating a bug related to authentication, use this skill to trace all relevant files from the initial entry point through to deep-level dependency modules and configuration manifests.

Quick Start

Use the finding-files skill to locate all files related to the authentication module based on the vocabulary defined in questions.md.

Frequently Asked Questions about finding-files

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

FAQPage Schema
How do I locate relevant files across multiple repositories when investigating a bug?

To locate relevant files across multiple repositories, you can use a multi-stage file discovery strategy that iterates through naming conventions, content patterns, dependency chains, and configuration manifests to ensure no relevant file is overlooked.

What is the best way to discover codebase components related to a specific investigation scope?

The best way to discover codebase components is by applying a structured, multi-layered search strategy that traces dependency chains and configuration manifests, requiring a defined vocabulary in questions.md to scope the search and ensure high-precision results.

Can I trace dependency chains and configuration manifests to find related modules in a large codebase?

Yes, you can trace dependency chains and configuration manifests by employing a multi-strategy search that uses globbing, content grepping, and directory exploration to navigate from an initial entry point through to deep-level dependency modules.

Does multi-repo codebase navigation require a predefined vocabulary to scope the search?

Yes, multi-repo codebase navigation requires a defined vocabulary in questions.md to scope the search and ensure high-precision results, allowing the multi-stage file discovery strategy to automatically scale operations across the defined project repositories.

What are the limitations of using naming conventions and content patterns for file discovery?

When using naming conventions and content patterns for file discovery, limitations arise if the search scope is not properly defined by a vocabulary in questions.md, which can reduce precision and cause relevant dependency modules or configuration manifests to be overlooked.