skills.rest
zcawood-mie
zcawood-mieCOMMUNITY
Explore all skills by this author →
GitHub

research

...

Updated Aug 23, 2026
Search Tags:#investigation#reporting#traceability#diagrams#data-flow#code-exploration#code-research
One-click install
npx skills add https://github.com/zcawood-mie/agentz --skill research-zcawood-mie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: research
Source: https://github.com/zcawood-mie/agentz/tree/main/skills/research
Command: npx skills add https://github.com/zcawood-mie/agentz --skill research-zcawood-mie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a repeatable, methodology-driven way to investigate codebases so engineers and reviewers can quickly understand how features are implemented, where data flows, and what patterns exist without ad-hoc, error-prone exploration.

Core Features & Use Cases

  • Methodical Investigation: Step-by-step research guidance from broad discovery to targeted file:line tracing.
  • Specialist Roles: Delegation patterns for CodeExplorer, DocFetcher, WebSearcher, GitHubOps, and CodeScanner to combine code inspection, documentation lookup, and external search.
  • Report & Diagram Guidance: Prescribes diagram types, reporting formats, and strict output rules (file paths, line numbers, tables, and rendered diagrams) for reproducible findings.
  • Use Cases: Feature implementation planning, root-cause debugging, architecture reviews, and producing handoff-ready research reports.

Quick Start

Ask the research skill to investigate how authentication is implemented in the repository, trace its data flow, list file:line references, recommend a diagram type, and return a concise findings section.

Frequently Asked Questions about research

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

FAQPage Schema
How do I trace data flow across a microservice codebase?▼

Tracing data flow across a microservice codebase involves methodical investigation from broad discovery to targeted file:line tracing, yielding evidence-backed findings with structured comparison tables and recommended diagram types.

What is the best way to investigate how a feature is implemented in a repository?▼

Investigating feature implementation is best done through a methodology-driven research process that delegates code inspection and documentation lookup, yielding reports with exact file paths, line numbers, and recommended diagram types.

Can I use this for root-cause debugging in single-repo applications?▼

Yes, this methodology supports root-cause debugging in single-repo applications by applying step-by-step code exploration and data-flow tracing to isolate issues and produce evidence-backed findings with precise file:line references.

Does code research work for generating architectural overviews and diagrams?▼

Code research works for generating architectural overviews by prescribing specific diagram types based on discovered implementation patterns, returning structured comparison tables and reproducible findings with file:line references.

How to produce a handoff-ready research report for code exploration?▼

Producing a handoff-ready research report requires applying methodical code investigation that enforces strict output rules, yielding structured formats with file paths, line numbers, comparison tables, and rendered diagrams.

Related Skills

Explore More Education & Research Skills→
az9713az9713

dark-code-suite-init

Initialize a project with dark code prevention directories, CLAUDE.md section, and baseline audit.

Community
Intermediate
rstacruzrstacruz
13

ralph-prepare

Break down feature plans into actionable tickets and a Mermaid dependency diagram.

Community
Intermediate
spkc83spkc83

python-code-assistant

Generate, analyze, debug, refactor, and test Python code locally using Jedi.

Community
Advanced
trmaphitrmaphi

datafusion-cli

Query Parquet, Arrow, IPC, and AVRO files with SQL via DataFusion CLI.

Community
Intermediate