How do I install the Code Search skill?

Run npx skillmds add trancong12102/code-search in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Code Search safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Code Search?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Code Search free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Code Search?

trancong12102 (@trancong12102) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Code Search by trancong12102 — Agent Skill

Name: Code Search
Rating: 4.5 (4 reviews)
Author: trancong12102

Code Search

Routes local codebase search to the right tool — keyword, semantic, or symbol. Use when searching a codebase for identifiers, tracing features across files, answering conceptual questions about local code, or exploring unfamiliar projects. Do not use for external docs, GitHub repos, or package lookups.

File contents

code-search

Pick the tool by the shape of the question:

Exact identifier known → mcp__plugin_ora_fff__grep. Naming variants of one identifier (e.g. ['ActorAuth', 'actor_auth']) → mcp__plugin_ora_fff__multi_grep.
File by name → mcp__plugin_ora_fff__find_files (frecency-ranked, git-dirty boosted).
Concept / "how does X work" / "where is Y handled" (no identifier yet) → mcp__plugin_ora_morph__codebase_search. One call replaces the grep→Read→grep loop; fall back to fff + Read only when it misses.
Symbol definition / all references → LSP.
Match by code structure rather than text → mcp__plugin_ora_ora__ast_search.
Map a file's or directory's symbols/exports/imports before reading → mcp__plugin_ora_ora__outline.
Git history / blame → git via Bash.

Morph returns a synthesized answer with file:line citations. The citations are real; the synthesis can misread what the code does — Read the cited locations before relaying load-bearing conclusions.

Don't grep a feature by OR-ing guessed synonyms; the real name gets missed and output drowns in noise. Learn the feature's actual name from README or directory structure, grep that one term, and follow references.

Frequently asked questions