locate

Trace shortest call paths and plan minimal file edits for code changes.

Updated Mar 2, 2026

Search Tags:#codebase #navigation #refactor #locate #change-set #call-path

Ready to run

npx skills add https://github.com/supermalang/ai-augmented-coding --skill locate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: locate
Source: https://github.com/supermalang/ai-augmented-coding/tree/main/.claude/skills/locate
Command: npx skills add https://github.com/supermalang/ai-augmented-coding --skill locate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a vague code-change request into a precise change-set plan so you can edit the smallest possible set of files without wasting time rediscovering the codebase structure.

Core Features & Use Cases

Change-Set Scoping: Identifies the minimal target files and line ranges needed for a requested tweak, fix, or improvement.
Call-Path Tracing: Follows the shortest entry-to-implementation path so the builder knows exactly where behavior starts and where it changes.
Edit Planning: Separates files to edit from files to read for context, and highlights ripples, shared types, and test coverage.
Use Case: When asked to speed up an export, fix a formatting bug, or adjust a command flow, this Skill produces a surgical map before implementation begins.

Quick Start

Ask the skill to locate the files and call path for your requested code change before you start editing.

Frequently Asked Questions about locate

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

FAQPage Schema

How do I find the exact files to change for a vague codebase refactor?▼

A change-set plan identifies the minimal target files and line ranges needed for a code tweak or refactor. It separates files to edit from context files, highlights ripples, and outlines the edit order before implementation begins.

How do I trace the shortest call path for a requested code change?▼

Call-path tracing follows the shortest entry-to-implementation route to show where behavior starts and changes. This maps the exact execution flow so you know precisely where to apply surgical edits.

What is the best way to plan a surgical change-set before editing a non-trivial codebase?▼

Planning a surgical change-set involves mapping target paths, context files, edit order, ripples, and tests without making file edits. This ensures you touch the smallest possible set of files.

Can I scope a code change and identify test coverage without modifying files?▼

Yes, you can scope a code change without modifying files because the process makes no file edits or side effects. It highlights test coverage and shared types while returning a precise target plan.

When do I need to scope a change-set plan instead of editing code directly?▼

You need to scope a change-set plan when working with non-trivial codebases requiring surgical fixes, refactors, or feature tweaks. It prevents wasting time rediscovering codebase structure for vague requests.