locating-code

Locate files, directories, and entry points relevant to a feature.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/ReadyStateChange/agents --skill locating-code-readystatechange
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: locating-code
Source: https://github.com/ReadyStateChange/agents/tree/main/skills/locating-code
Command: npx skills add https://github.com/ReadyStateChange/agents --skill locating-code-readystatechange

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly locate where code lives, including entry points, tests, and configs, to answer questions like "where does X live?" or "which files touch Y?".

Core Features & Use Cases

  • Group findings by purpose (implementation, tests, config) and surface likely entry points.
  • Locate files, directories, and entry points relevant to a feature or question, enabling efficient navigation.

Quick Start

Find where a feature or file lives and list relevant implementation, tests, and config.

Frequently Asked Questions about locating-code

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

FAQPage Schema
How do I locate where a specific feature is implemented in a codebase?

To locate where a feature is implemented, this Skill searches the codebase to identify relevant files and groups findings by purpose, surfacing implementation locations and related directories.

How do I find entry points and related tests for a component?

Finding entry points and related tests involves locating files that touch a specific component and grouping them by purpose to surface likely entry points alongside relevant test and config files.

What is the best way to navigate which files touch a specific component?

The best way to navigate which files touch a component is to locate entry points and relevant directories, grouping the discovered implementation and test files by their functional purpose.

Can I use this to locate config files related to a specific question?

Yes, you can locate config files related to a specific question by searching the codebase to identify and group relevant implementation, test, and configuration locations together.

When do I need to group codebase findings by purpose?

You need to group codebase findings by purpose when answering where a feature lives or which files touch a component, ensuring implementation, tests, and config are clearly separated for efficient navigation.