pilinux/gorest · Archived

source-search

Fast, repository-wide search to locate symbols, routes, env vars, error codes, and other artifacts (read-only).

First seen Mar 2, 2026

Installation

$ npx skills add pilinux/gorest --skill source-search

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from pilinux/gorest · top by installs.

npx skills add pilinux/gorest

Browse all from pilinux/gorest

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 502
License LICENSE
Default branch main
Open issues 0
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

LicenseMIT
More metadata
mode
read-only
purpose
search

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,148 B
  • docs SUMMARY.md 132 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 6 installs

SKILL.md

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

  1. Identify exact search keys and likely variants.
  2. Glob by folder or pattern to limit scope.
  3. Grep and rank results by relevance.
  4. 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)