viz

Investigate codebases read-only to explain components with file and line citations.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/arnavsurve/dotfiles --skill viz-arnavsurve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: viz
Source: https://github.com/arnavsurve/dotfiles/tree/main/agents/skills/viz
Command: npx skills add https://github.com/arnavsurve/dotfiles --skill viz-arnavsurve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read-only investigation of topics in the current codebase to understand how something works without making changes or edits.

Core Features & Use Cases

  • Read filenames, line numbers, and code snippets to understand how components interact.
  • Identify data flows, dependencies, and configuration paths without modifying the repository.
  • Use case: when evaluating how authentication flows or database handling works, you can gain a grounded picture without touching files.

Quick Start

Explain how a topic works in the codebase by listing relevant filenames, line numbers, and code snippets without editing any files.

Frequently Asked Questions about viz

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

FAQPage Schema
How do I investigate how authentication flows work in a codebase?

To investigate an authentication flow in a codebase, you can perform a read-only exploration that reads filenames, line numbers, and code snippets to understand component interactions without modifying files.

Can I trace database handling logic without modifying the repository?

Yes, you can trace database handling logic without modifying the repository by using static code exploration to identify data flows, dependencies, and configuration paths with citations to file paths.

What is the best way to understand codebase interactions without making runtime changes?

The best way to understand codebase interactions without runtime changes is static code exploration, which lists relevant code snippets and line numbers to provide a grounded picture of how components work.

Does read-only codebase exploration provide citations for configuration paths?

Yes, read-only codebase exploration provides citations for configuration paths by referencing exact file paths and line numbers, ensuring you can verify data flows and dependencies without editing files.

What are the limitations of static code exploration for understanding component interactions?

The main limitation of static code exploration for understanding component interactions is that it requires no runtime changes, meaning it cannot capture dynamic execution behavior or test active data flows in real-time.

How do I explore configuration paths across a repository step by step?

To explore configuration paths across a repository step by step, conduct a read-only investigation that reads code snippets and line numbers to map dependencies and data flows without touching files.