locating-code

Locate code files by topic and categorize them by purpose with full paths.

4|1|Updated Oct 29, 2025
One-click install
npx skills add https://github.com/samjhecht/wrangler --skill locating-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: locating-code
Source: https://github.com/samjhecht/wrangler/tree/main/skills/locating-code
Command: npx skills add https://github.com/samjhecht/wrangler --skill locating-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps locate and documents where code lives, helping you quickly map out files by topic and categorize by purpose.

Core Features & Use Cases

  • Find files by topic: locate code related to features
  • Categorize findings: implementation, tests, configs, docs
  • Return structured results: group by purpose with full paths

Quick Start

Run: locate code related to 'authentication' and list results.

Frequently Asked Questions about locating-code

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

FAQPage Schema
How do I locate code by feature or topic in an unfamiliar codebase?

Use search strategies like grep and glob patterns to locate code by topic, then organize results by purpose—implementation, tests, config, docs—with full file paths. This maps where related files live across your repository structure.

What's the best way to find implementation, test, and configuration files together?

Apply pattern-aware directory exploration targeting common naming conventions like *service, *handler, *controller, *test, and *config, combined with filesystem searches in standard locations (src/, lib/, pkg/). Results group findings by purpose with counts.

Can I use search strategies to navigate a large repository without knowing its structure?

Yes. Codebase navigation using grep, glob, and language-aware directory patterns identifies implementation and supporting files by topic without prior knowledge of repository layout, returning a structured map organized by file purpose.

How do I document where code lives for quick reference?

Generate a structured categorized map showing code locations by feature with full paths and file counts. This documentation enables rapid navigation when returning to unfamiliar repositories or onboarding to new codebases.

What file patterns should I search for when locating feature-specific code?

Search for naming patterns like *service, *handler, *controller for implementation; *test for tests; *config for configuration; and *types for type definitions. Combined with directory exploration in src/, lib/, and pkg/, these patterns surface all related code locations.