discover-source

Guide phased codebase exploration and generate structured discovery artifacts.

1|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/qmu/workaholic --skill discover-source
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: discover-source
Source: https://github.com/qmu/workaholic/tree/main/plugins/core/skills/discover-source
Command: npx skills add https://github.com/qmu/workaholic --skill discover-source

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps AI agents systematically surface and organize codebase context for a ticket by providing structured discovery guidelines.

Core Features & Use Cases

  • Phase-based exploration guidance: Direct matches, import-chain analysis, usage discovery, related tests, and configuration discovery.
  • Depth-limited analysis: Maintain relevance and manage noise by applying per-phase limits.
  • Produces structured discovery artifacts: summary, files, snippets, import_graph, code_flow, test_coverage, and references.

Quick Start

To apply this Skill, follow the guided source-discovery steps when planning a ticket, and adapt the workflow to your repository. For example: locate direct source files, trace dependencies, and extract representative code snippets to inform decisions.

Frequently Asked Questions about discover-source

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I systematically explore a codebase to gather context for a new ticket?

Codebase exploration for tickets works through a phased workflow: locating direct file matches, tracing import chains, discovering usage patterns, and extracting related tests. It outputs structured artifacts including summaries, import graphs, and code flow patterns.

What is the best way to analyze import chains and dependencies during source discovery?

Import chain analysis during source discovery involves tracing dependencies from direct file matches outward while applying depth limits to manage noise. This generates an import_graph artifact mapping module connections across the repository.

How do I extract code snippets and test coverage details when planning a development task?

Extracting code snippets and test coverage details involves locating representative code sections and related tests within the codebase. The discovery process outputs these as structured artifacts, providing necessary context for informed decision-making.

Can I limit the exploration depth to manage noise when discovering project context?

Yes, you can limit exploration depth to manage noise and maintain relevance. The discovery workflow applies per-phase depth controls, ensuring import-chain analysis and usage discovery remain focused without overwhelming generated context artifacts.

What structured artifacts are produced when discovering source files and configuration schemas?

Discovering source files and configuration schemas produces a structured artifact set including summary, files, snippets, import_graph, code_flow, patterns, and test_coverage. These artifacts organize discovered context for systematic review.