Skip to content

JPeetz/agent-skills / skills/development/finding-unknowns/skills/reference-hunt

reference-hunt

Verified

Use when user points at code and says "like this."

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.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 319kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 319kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 319kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 319kUpdated Claude CodeCodexVerifiedInstall