pipeline-code-researcher

Explore codebases read-only to surface patterns, imports, and structure.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/daniyarseifolla/agent-skills --skill pipeline-code-researcher
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pipeline-code-researcher
Source: https://github.com/daniyarseifolla/agent-skills/tree/main/v2.2/pipeline/code-researcher
Command: npx skills add https://github.com/daniyarseifolla/agent-skills --skill pipeline-code-researcher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read-only haiku agent that performs lightweight codebase exploration to surface patterns, imports, and file structure without modifying code, enabling fast reconnaissance before deeper analysis.

Core Features & Use Cases

  • Lightweight, read-only codebase exploration to locate imports, patterns, and file structure across large projects.
  • Efficient pre-coding reconnaissance for L/XL tasks, enabling planners and coders to quickly summarize code health and architecture.
  • Targeted queries with scope and focus controls to limit search to relevant modules.

Quick Start

Instruct the haiku-powered explorer to scan the target module with a focus on imports and patterns in a read-only mode.

Frequently Asked Questions about pipeline-code-researcher

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

FAQPage Schema
How do I perform read-only codebase exploration before starting a large refactoring task?

Read-only codebase exploration uses a lightweight haiku agent to scan your project, surfacing file structures, imports, and patterns without modifying code. This enables fast reconnaissance to summarize architecture before deeper analysis or refactoring.

Can I do lightweight code reconnaissance for L/XL tasks without modifying the source files?

Yes, lightweight code reconnaissance for L/XL tasks is strictly read-only. It enforces constraints to prevent code modification, allowing you to safely locate imports and map file structure across large projects.

What is the best way to surface codebase patterns and imports for downstream planning?

The best way to surface codebase patterns for downstream planning is using a targeted, haiku-based search with scope controls. It returns a structured summary of imports and architecture suitable for coders and planners.

Does this codebase analysis approach work for quickly summarizing code health and architecture?

Yes, this codebase analysis approach works for quickly summarizing code health and architecture. It performs efficient pre-coding reconnaissance to locate patterns and file structure, enabling planners to assess project state.

How do I limit my codebase exploration to only relevant modules and specific file structures?

You limit codebase exploration to relevant modules using targeted queries with scope and focus controls. This restricts the read-only search to specific areas, efficiently locating imports and patterns without scanning the entire project.