code-search-navigation
Skill2 starsChanged 4 months agoMITView on GitHub
Use when an agent needs to locate relevant files, symbols, call sites, routes, tests, configs, or ownership boundaries before editing or explaining code.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- zavora-ai/skill-code-search-navigationtheir own version, first seen May 31, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- zavora-ai/skill-code-search-navigation★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository42 other files it gives its agents.
- architect-boundary-reviewSkill
- architect-decision-recordSkill
- architect-system-designSkill
- browser-playwright-checkSkill
- browser-useSkill
- controlled-emergence-observerSkill
- dev-code-locationSkill
- dev-small-scope-patchSkill
- dev-test-and-explainSkill
- eval-observation-writingSkill
- eval-promotion-adviceSkill
- eval-risk-gap-analysisSkill
- ops-log-diagnosisSkill
- ops-runtime-healthSkill
- ops-stuck-workflowSkill
- pm-acceptance-criteriaSkill
- pm-architecture-reviewSkill
- pm-delivery-planSkill
- pm-evolve-skillsSkill
- pm-long-horizon-planningSkill
- pm-priority-triageSkill
- pm-product-design-briefSkill
- pm-product-requirementsSkill
- pm-scope-controlSkill
- pm-solve-problemsSkill
- pm-tech-scopeSkill
- qa-regression-checkSkill
- qa-reproduce-issueSkill
- qa-verify-fixSkill
- run-local-command-checkSkill
- test-selectionSkill
- tm-delivery-governanceSkill
- tm-review-routingSkill
- tm-risk-dependencySkill
- ui-information-architectureSkill
- ui-requirementsSkill
- ui-usability-acceptanceSkill
- ui-visual-consistencySkill
- web-extractSkill
- web-researchSkill
- web-searchSkill
- windows-useSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 10 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use before changing or explaining code when the relevant entry point, module, test, route, or ownership boundary is not already known.
- Very specific: line 15
Prefer rg and rg --files for text and file discovery.
- Distinctive: line 16
Search for exact identifiers, route paths, filenames, error text, and user-visible labels.
- Distinctive: line 17
Read nearby code before editing.
- Distinctive: line 18
Follow existing patterns before adding new abstractions.
- Distinctive: line 19
Keep the discovered evidence narrow: file paths, line numbers, and why they matter.
- Distinctive: line 20
Stop searching once the implementation boundary is clear.
- Distinctive: line 26
Search terms or discovery method.
- Distinctive: line 33
Do not edit before locating the owning module unless the task is trivial and file ownership is explicit.
- Distinctive: line 34
Do not perform broad refactors just because search found related code.
- Distinctive: line 35
Do not cite files you did not inspect.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Code Search Navigation
When to use
Use before changing or explaining code when the relevant entry point, module, test, route, or ownership boundary is not already known.
Rules
- Prefer
rgandrg --filesfor text and file discovery. - Search for exact identifiers, route paths, filenames, error text, and user-visible labels.
- Read nearby code before editing.
- Follow existing patterns before adding new abstractions.
- Keep the discovered evidence narrow: file paths, line numbers, and why they matter.
- Stop searching once the implementation boundary is clear.
Required output
When reporting, include:
- Search terms or discovery method.
- Key files inspected.
- Chosen edit boundary.
- Any relevant files intentionally left untouched.
Forbidden actions
- Do not edit before locating the owning module unless the task is trivial and file ownership is explicit.
- Do not perform broad refactors just because search found related code.
- Do not cite files you did not inspect.
Minimal example
Search: rg "resolveAndInject" packages/codeflowmu-runtime/src
Found: TaskDispatcher.ts builds the agent prompt prefix
Boundary: route skill injection there, not in Panel renderingDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.