skills.rest
adrielp
adrielpCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

codebase-locator

Locate and inventory codebase files by feature with absolute paths and category counts.

20|6|Updated Jan 16, 2026
Search Tags:#codebase#find#project-structure#repo#locate#feature-map
One-click install
npx skills add https://github.com/adrielp/ai-engineering-harness --skill codebase-locator-adrielp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codebase-locator
Source: https://github.com/adrielp/ai-engineering-harness/tree/main/pi/skills/codebase-locator
Command: npx skills add https://github.com/adrielp/ai-engineering-harness --skill codebase-locator-adrielp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Locating where code lives across a codebase is often manual, error-prone, and time-consuming; this skill provides organized mappings of files and components by feature or task without analyzing content.

Core Features & Use Cases

  • Comprehensive File Discovery: multi-pattern searches to identify files by feature, technology, or architectural role across common and framework-specific locations.
  • Intelligent File Categorization: group files into Implementation, Test, Configuration, Documentation, and Type Definitions for quick navigation.
  • Structured Location Reporting: produce absolute paths, cluster related directories, and quantify discoveries by category.

Quick Start

Provide a repository path or project context and I will return a structured map of codebase locations.

Frequently Asked Questions about codebase-locator

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

FAQPage Schema
How do I locate files across a codebase by feature or architectural role?▼

Mapping codebase structure involves inventorying files by feature or architectural role across framework-specific locations. This process groups files into categories like Implementation, Test, and Configuration to provide quick navigation without analyzing file content.

What is the best way to map project structure for a large repository?▼

Mapping project structure involves inventorying files by feature or architectural role across framework-specific locations. This process groups files into categories like Implementation, Test, and Configuration to provide quick navigation without analyzing file content.

Can I find specific services and configurations across multiple framework layers?▼

Providing a repository path or project context triggers a structured map of codebase locations. The skill inventories relevant files and reports absolute paths, cluster related directories, and quantifies discoveries by category breakdowns.

How do I get a structured report of absolute paths and category counts for my repo?▼

Providing a repository path or project context triggers a structured map of codebase locations. The skill inventories relevant files and reports absolute paths, cluster related directories, and quantifies discoveries by category breakdowns.

Does this codebase locator analyze the content of the files it finds?▼

No, it does not analyze file content. The codebase locator strictly focuses on comprehensive file discovery and intelligent categorization, mapping where features live without inspecting the internal code logic.

Related Skills

Explore More Software Engineering Skills→
PiklarPiklar

speckit-clarify

Identifies specification ambiguities and resolves them via interactive clarification workflow.

Community
Advanced
poteto-gopoteto-go
3

test-driven-development

Enforce test-first development with RED-GREEN-REFACTOR cycles across Go projects.

Official
Intermediate
audibleblinkaudibleblink
4

grepai

Perform semantic code search and trace call relationships across codebases.

Community
Advanced
tianxiao1430-jpgtianxiao1430-jpg
17

zread-expert

Analyze GitHub repositories with Zread MCP for structural audits and architecture reviews.

Community
Advanced