/reference-seek

name: reference-seek
description: |
  This skill should be used when the user asks to "find references", "참고할 만한 거",
  "similar implementation", "오픈소스 있나", "how others do this", "레퍼런스 찾아줘",
  or needs to find existing patterns (internal) and open-source examples (external)
  for implementing a feature.
version: 2.0.0
validate_prompt: |
  Must contain all of these sections:
  - Internal References section (with content or "No existing patterns found" message)
  - GitHub References section with at least 1 repo entry including stars, license, and updated date
  - At least 1 repo with actual code excerpt (Key Code block with real source lines)
  - Usage Suggestions section with numbered recommendations
  Output must start with "## Reference Seek:" header.

Reference Seek - Find Implementation References (v2.0.0)

Find internal patterns, quality-filtered GitHub repos with code-level insights, official docs, and external examples.

Purpose

When building a feature, find what you can **reuse** or **learn from**:

• Internal: Existing patterns in the codebase
• GitHub: Quality-filtered repos with actual code excerpts
• Official Docs: context7-powered library documentation
• External: Blog posts, tutorials, best practices

Runtime Surface

Claude Code

• Use `Task(Explore)`, `gh`, context7 MCP when available, and `WebSearch` as

described below.

Codex

• Map internal codebase search to `hoyeon-code-explorer` when installed.
• Use Bash-first `gh api` and `curl` for GitHub discovery and code excerpts.
• Do not require context7 MCP for v1; use it only if already available in the

current runtime. Otherwise, use official docs via the available Codex web search/fetch surface and label that fallback.

• If no native subagent adapter is loaded, perform the internal search directly

with `rg` and targeted file reads.

Use Cases

• "Looking to implement OAuth login — any good references?"
• "Find references for implementing a rate limiter"
• "How do I implement pagination? Find me some references"
• "Any open source projects similar to WebSocket connection management?"

Execution

Step 0: Dependency Check + Topic Classification (1 message)

Run in parallel:

**0-A. gh auth check:**

gh auth status

| Result | Variable | |--------|----------| | Authenticated | `GH_AVAILABLE=true` | | Not authenticated / gh not found | `GH_AVAILABLE=false` |

**0-B. Topic extraction + classification (reasoning, same message):**

Extract from user request:

• `TOPIC`: Normalized English topic (e.g., "rate limiting", "OAuth authentication")
• `TOPIC_CLASS`: `library` | `pattern` | `concept`
• `GH_QUERY`: GitHub search query (e.g., `rate+limiter`, `oauth+middleware`)
• `GH_LANG_FILTER`: Language filter inferred from codebase (e.g., `+language:typescript`)
• `CONTEXT7_LIB`: Library name for context7 resolve (if `library` class, use directly; otherwise best guess or skip)

Examples:

• "any rate limiter references?" → TOPIC: `rate limiting`, CLASS: `pattern`, GH_QUERY: `rate+limiter+middleware`, CONTEXT7_LIB: `rate-limiter-flexible`
• "NextAuth implementation references" → TOPIC: `NextAuth authentication`, CLASS: `library`, GH_QUERY: `nextauth+authentication`, CONTEXT7_LIB: `next-auth`
• "pagination references" → TOPIC: `pagination implementation`, CLASS: `pattern`, GH_QUERY: `pagination+cursor`, CONTEXT7_LIB: skip

Step 1: Parallel Search (1 message, up to 4 sources)

**CRITICAL**: Run all available tracks in **one message** in parallel.

| Track | Tool | Purpose | |-------|------|---------| | 1-A | `Task(Explore)` | Internal codebase pattern search | | 1-B | `Bash: gh api search/repositories` | GitHub repo search (stars-sorted, top 10) | | 1-C | `mcp__context7__resolve-library-id` | Library docs ID lookup | | 1-D | `WebSearch` | Blog/tutorial search (1 query only) |

**1-A. Internal Search (Explore agent):**

Task(subagent_type="Explore",
     prompt="""
Find existing patterns related to [{TOPIC}] in this codebase.
Look for:
- Similar implementations or utilities
- Patterns that could be reused or extended
- Related helper functions or modules

Report as file:line format with brief description of what's reusable.
""")

**1-B. GitHub Search (only if GH_AVAILABLE=true):**

gh api "search/repositories?q={GH_QUERY}+{GH_LANG_FILTER}&sort=stars&per_page=10" \
  --jq '.items[] | select(.archived == false) | {
    full_name, stars: .stargazers_count, lang: .language,
    topics, license: .license.spdx_id, desc: .description,
    pushed: .pushed_at, url: .html_url, default_branch
  }'

**1-C. context7 resolve (if CONTEXT7_LIB is set):**

mcp__context7__resolve-library-id(libraryName="{CONTEXT7_LIB}")

**1-D. WebSearch (1 query only):**

WebSearch: "{TOPIC} implementation tutorial best practices 2024 2025"

**When GH_AVAILABLE=false:** Skip 1-B. Run WebSearch 3 times instead (v1.0 fallback):

WebSearch: "{TOPIC} implementation github"
WebSearch: "{TOPIC} open source example"
WebSearch: "{TOPIC} tutorial best practices"

Add warning at top of output: `> ⚠️ GitHub API unavailable (gh not authenticated). Results from web search only.`

Step 2: Quality Filter + context7 Query (sequential after Step 1)

**2-A. Quality Filter (reasoning, applied to 1-B results):**

| Criteria | Threshold | |----------|-----------| | Stars | >= 100 (relax to >= 50 if fewer than 2 pass) | | Last push | Within 24 months | | License | MIT, Apache-2.0, BSD-2-Clause, BSD-3-Clause, ISC, MPL-2.0 | | Archived | Excluded (already filtered by jq) |

→ Top 5 passing repos = `QUALIFIED_REPOS` → Top 1-2 repos = `DEEP_DIVE_TARGETS`

If all repos filtered out: relax stars to >= 50. If still none, take top 3 with warning badge `⚠️ Below quality threshold`.

**2-B. context7 docs query (only if 1-C resolve succeeded):**

mcp__context7__query-docs(
  libraryId="{resolved_id}",
  query="{TOPIC} implementation patterns examples"
)

If resolve failed in 1-C, skip this step entirely.