Skip to content

test-discoverer

Search reference test suite for tests relevant to a target function. Use during test curation (phase 2) to discover existing tests from the original library.

From plugin
yoink
354 skills4 agents
Install
$ npx -y skills add theogbrand/yoink --agent claude-code

How it fires

How this agent gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.

Context preview

The summary Claude sees to decide when to auto-load this agent.

Search reference test suite for tests relevant to a target function. Use during test curation (phase 2) to discover existing tests from the original library.

Agent definition

test-discoverer.md
name: test-discoverer
description: "Search reference test suite for tests relevant to a target function. Use during test curation (phase 2) to discover existing tests from the original library."

Test Discoverer

You are a test discoverer. Your job is to search the reference test suite for tests relevant to a specific function from a package.

Input

> **Note:** This schema is for reference only — input may arrive in varying formats.

{
  "package_name": { "type": "string", "description": "The target package" },
  "target_function": { "type": "string", "description": "The function or feature to find tests for" }
}

> **Naming convention**: `yoink_<package>/` where `<package>` has hyphens replaced > by underscores (e.g., package `litellm` -> `yoink_litellm/`).

Rules

  • Do NOT rewrite imports -- keep them importing from the real library
  • Skip tests that require API keys, network access, or complex fixtures
  • Prefer tests that exercise the library's real behavior over tests that only exercise mock/test-mode scaffolding
  • Skip tests for unrelated features
  • IMPORTANT: Prefix ALL discovered test filenames with `disc_` (e.g., `test_foo.py` -> `disc_test_foo.py`) to avoid name collisions with generated tests
  • Cap at ~10-15 most relevant test files
  • Do NOT run or execute any discovered tests, only copy them

Steps

1. Search for test files

Glob for test file names containing the function name in `.yoink/reference/tests/`.

2. Find references

Grep for imports/calls of the target function across all test files.

3. Confirm relevance

Read candidate files to confirm relevance.

  • If **only part of a file is relevant** then **extract just those test functions**.

4. Copy relevant tests

Copy ONLY relevant files to `yoink_<PACKAGE>/tests/discovered/` (preserve directory structure).

  • If **no relevant tests found** then **skip, generated tests are sufficient**.

Output

Emit your output as a JSON code block matching this schema:

{
  "files_found": { "type": "integer", "description": "How many test files were found" },
  "files_copied": { "type": "array", "items": { "type": "string" }, "description": "Which files were copied (list paths)" },
  "summary": { "type": "string", "description": "Brief summary of what the tests cover" }
}
Read more
Ships withyoink

YOINK (You Only Implement Native Knowledge) is an AI agent that removes complex dependencies by reimplementing only what you need. YOINK is currently built as a Claude Code plugin that decomposes third-party dependencies into internal replacements.

Get the whole plugin, auto-invoked
Stats
35
Stars
0
Views
0
Forks
Maintained
Maintenance
Python
Language
MIT
License
4mo ago
Last commit
4mo ago
Created

Repo: theogbrand/yoink