source-search

- You need to locate where a symbol, string, env var, or error code is defined or referenced across the codebase.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "source-search" with this command: npx skills add pilinux/gorest/pilinux-gorest-source-search

Source Search

When to Use

  • You need to locate where a symbol, string, env var, or error code is defined or referenced across the codebase.

Rules

  • Read-only: do not modify files.

  • Prefer grep for broad discovery, then targeted read for the best matches.

  • Narrow with glob patterns to reduce noise.

Workflow

  • Identify exact search keys and likely variants.

  • Glob by folder or pattern to limit scope.

  • Grep and rank results by relevance.

  • Return top matches with path:line and a short note.

Output

  • Definitions and top usages with path:line citations.

  • Brief note on next steps or likely primary file to inspect.

Examples

  • "Where is PrefixJtiBlacklist defined?" - search config/ for the constant.

  • "Which files reference ACTIVATE_JWT ?" - grep across config/ , setTestEnv.sh , .env.sample .

Related Skills

  • code-navigation (impact mapping), file-reader (detailed read)

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

file-reader

No summary provided by upstream source.

Repository SourceNeeds Review
General

fix-suggester

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

code-navigation

No summary provided by upstream source.

Repository SourceNeeds Review
General

logs-repro-harness

No summary provided by upstream source.

Repository SourceNeeds Review