reference-hunt
/reference-hunt
Use existing source code as the specification when the user can't describe what they want in words. Use when the user points at a library, module, folder, or site and says "like this," even if it's in a different language or stack.
- Author
- Neeeophytee ↗
- Repository
- finding-unknowns-skills ↗
- Licence
- MIT
- Last repository change
- 28.09.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 28.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use existing source code as the specification when the user can't describe what they want in words. Use when the user points at a library, module, folder, or site and says "like this," even if it's in a different language or stack.
Triggers from the description
Original author description
Use existing source code as the specification when the user can't describe what they want in words. Use when the user points at a library, module, folder, or site and says "like this," even if it's in a different language or stack.
How it works
- Steps
- Guardrails
SKILL.md preview
--- name: reference-hunt description: Use existing source code as the specification when the user can't describe what they want in words. Use when the user points at a library, module, folder, or site and says "like this," even if it's in a different language or stack. --- # Reference hunt Some requirements are too intricate or too tacit to write down, but working code somewhere already embodies them. The best reference is not a screenshot or a description — it's source. Read it like a spec, then reimplement the semantics, not the syntax. ## Steps 1. Get the reference: a repo path, a vendored folder, a library name, or a site whose underlying code can be read. Ask what specifically to extract from it — behavior, structure, visual system, API shape — so you don't imitate the wrong dimension. 2. Read the reference and produce a **semantics summary** before writing any code: - the behaviors and guarantees it implements (timing, ordering, error handling, edge cases), - the decisions that look deliberate versus incidental, - anything that won't translate to the target language or stack, with a proposed equivalent. 3. Have the user confirm the semantics summary. This is the moment misreadings get caught cheaply. 4. Reimplement in the target stack: same semantics, native idioms. Do not transliterate line by line, and do not copy code verbatim from references whose license doesn't allow it — note the license if it's unclear. 5. Close the loop: list each behavior from the summary and where the new implementation honors it, plus any place you consciously diverged and why. ## Guardrails - The reference defines *what*; the target codebase's conventions define *how*. - If the reference itself turns out to be buggy or inconsistent, surface that instead of faithfully reproducing the bug. - Respect licenses: extracting semantics is fine; copying incompatible code is not.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · Neeeophytee/finding-unknowns-skills | 90 | MIT |
| namedtoaster/the-last-mile | 100 | MIT |
| GreatMark/fable-field-guide-skills | 100 | MIT |
Identical content appears in 2 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version c9d500f4ffd1 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 81implement
Implements a piece of work from a spec or ticket set. Use when the user says \"implement this spec\", \"work the tickets\", or wants code written from an existing plan. - 100library-analyzer
Use when the user wants to contribute to an open-source library, says "analyze this library for contribution", "I want to contribute to X", "help me contribute to", "contribution readiness", or "기여하고 싶다". Do NOT activate for general "how does X work" questions (use deepwiki-cli instead). - 100stack-branch
Create a new branch stacked on another PR. Use when you want to start work that depends on an existing PR that hasn't been merged yet. - 100bug-hunt
Proactively hunt latent defects across a feature/module by reading source and tracing data flow. Use to find bugs before they ship. Distinct from debugging a known failure or reviewing a diff. - 100bug-hunt
Proactively hunt latent defects across a feature/module by reading source and tracing data flow. Use to find bugs before they ship. Distinct from debugging a known failure or reviewing a diff. - 100feature
Add a feature to an existing project with a full sprint. Skips /think diagnostic, goes straight to planning. Use when the user knows what they want and the project already exists. Triggers on /feature.