Best use case

find-source is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Teams using find-source should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/find-source/SKILL.md --create-dirs "https://raw.githubusercontent.com/dlt-hub/dlt/main/tests/workspace/cli/ai/cases/mock_toolkit/skills/find-source/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/find-source/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How find-source Compares

Feature / Agentfind-sourceStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

This skill provides specific capabilities for your AI agent. See the About section for full details.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

Find a source.

Related Skills

worktree-make-dev

5182
from dlt-hub/dlt

Set up a dev environment in an existing worktree (make dev + copy secrets)

worktree-from-issue

5182
from dlt-hub/dlt

Create a git worktree with a new branch for implementing a fix or feature for a GitHub issue

switch-worktree

5182
from dlt-hub/dlt

Switch the current session to work in an existing git worktree

review-pr

5182
from dlt-hub/dlt

Analyze a GitHub pull request including diff, comments, related issues, and local code context

release-notes

5182
from dlt-hub/dlt

Generate release notes between two git tags with categorized PR summaries and author attribution

optimize-code

5182
from dlt-hub/dlt

Analyze and optimize Python code performance in critical paths

implement-issue

5182
from dlt-hub/dlt

Triage, plan, and implement a fix or feature for a GitHub issue end-to-end

dashboard

5182
from dlt-hub/dlt

Use when reading, editing, or creating files in dlt/_workspace/helpers/dashboard/ or tests/workspace/helpers/dashboard/ or tests/e2e/

create-worktree

5182
from dlt-hub/dlt

Create or reuse a git worktree for a pull request or branch so reviews and work happen in isolation

auto-write-test-rules

5182
from dlt-hub/dlt

Use when adding or proposing a new test ONLY if the test rules are not present

auto-import-rules

5182
from dlt-hub/dlt

Enforces dlt import conventions and ordering. Use when writing or modifying Python imports in dlt/ or tests/.

auto-docstring-rules

5182
from dlt-hub/dlt

Enforces dlt docstring conventions. Use when writing or modifying docstrings, classes, or function signatures in Python files.